Rebuild, White Label or Own the Code: The True Costs for an Established Money Transfer Operator

Most build-versus-buy guides are written for founders with a blank page. An established operator does not have a blank page. You have a licence, customers, corridors, partners, staff who know the current system, and years of records that must survive whatever you choose. That changes the arithmetic.

This guide is for founders, CTOs and finance leads at operators whose current platform has become slow or costly to change. It compares three paths: rebuild in-house, move to a white label platform, or move and own the source code. Where we quote RemitSo prices, they are the published ones. Where we estimate the cost of building, the figures are illustrative and labelled as such; replace them with your own.

A start-up choosing a platform is choosing where to begin. An established operator is choosing where to move, and every path includes a migration. That has three consequences.

• Every option carries a migration cost. Even a rebuild must move customers, recipients, compliance records and open balances off the old system. A guide that compares build costs with white label fees and ignores the move is comparing the wrong things.
• The old system keeps costing money until you leave it. Vendor fees, change requests and manual workarounds continue throughout. The longer a path takes, the more of those you pay twice.
• You already know what you need. You have a list of things the current platform cannot do. That list is the specification, and it lets you test each path against real requirements rather than a sales deck.

If you are still deciding whether to move at all, start with when an established operator should migrate.

Rebuild in-house. Your own engineers, employed or contracted, build a new platform that you own outright. You decide every feature and carry every risk: architecture, security, compliance logic, payment and payout integrations, apps, the admin panel, hosting and the migration.

Move to white label. You run your business on an existing remittance platform, in your brand, configured for your corridors, fees, rates and compliance rules. The provider builds and maintains the platform; your team runs the business on it. You pay a setup fee and a monthly platform fee.

Own the source code. You buy the code of an existing platform so your own engineers can change and extend it. You start from working software rather than a blank page, and you gain the control of a rebuild without its first years. In exchange, you need an engineering team able to own what you bought.

These are not mutually exclusive over time. An operator can move to white label now and buy the source code later, when the business needs to build things of its own on top. For what owning the code involves day to day, see owning your remittance source code.

The cost of a rebuild is mostly people multiplied by time. The hard part is being honest about the time. A remittance platform is not one product; it is several that must agree with each other to the cent:

• customer apps for iOS, Android and web, with identity checks, sign-in security and payment flows;
• a transfer engine that tracks every state from quote to payout, including failures, retries and reversals;
• integrations with payment, payout, identity check and rate partners, each with its own quirks;
• compliance: sanctions screening, risk rules, limits, document requests and regulator reports;
• double-entry accounting and deposit matching;
• an admin panel with roles and permissions, alerts, logs and maintenance controls;
• hosting, security testing, monitoring and the evidence an auditor will ask for.

The point of the table is not the total. It is the shape: a large cost before anything goes live, a period of paying for two systems, and a permanent team afterwards. Rebuilding can still be right, but only if the control it buys is worth that shape.

The cost profile of white label is the opposite of a rebuild: a modest setup fee, then a monthly fee that rises with your volume. RemitSo publishes its prices on the pricing page:

There is no revenue share. The fee is charged on completed transfers, so it tracks the business rather than a headcount. Hosting sits in your own AWS account, so you see that cost directly rather than through a mark-up.

What you still pay for on this path: your own partner contracts (banks, payout partners, identity checks), the engineering hours you choose to use, and your team's time during the move. RemitSo's migration is staged: RemitSo migrates your data, your team runs a trial and, if it wants, its own parallel run, and you launch first with a focused group of customers before migrating the rest. See migrating without losing customers.

RemitSo's source code is priced at $77,999 once, or $20,000 a year for five years. Details are on the source code pricing page.

Owning the code makes sense when you want to build things of your own on a working base: a product line, an internal tool, a deep integration with another part of your group. It also answers a board question that white label cannot fully answer: what happens to the platform if our relationship with the provider changes?

The price of the code is not the whole cost. You need people who can read, change, test, deploy and secure it. A small team is enough to extend a working platform; it is not enough to neglect one. Before you buy, ask what updates, documentation and support come with the licence, and how your changes will sit alongside future releases.

The operator and every figure not taken from RemitSo's published prices are illustrative, not drawn from any real business.

An operator runs about 4,000 completed transfers a month on a vendor platform and expects about 7,000 by year three. The board asks the CTO to compare three-year costs.

White label. Setup $7,999. Year one at 4,000 transfers falls in the $499 band: $5,988. Volume passes 5,000 early in year two, so years two and three sit in the $999 band: $23,976. Platform total over three years: $37,963. The CTO assumes 20 engineering hours a month at $25, about $18,000 over three years. AWS is billed to the operator and depends on usage, so it is listed separately.

Own the source code. $77,999 once, or $100,000 over five years on the yearly option. The CTO assumes a team of three engineers at 7,000 a month each, fully loaded: 756,000 over three years. That team builds things the business wants, so the question is not "is this cheaper?" but "is what they would build worth it?"

Rebuild. Using the illustrative estimate above, 864,000 before the first live transfer, 18 months of old-system costs alongside, then the ongoing team.

The board chooses white label now and puts the source code decision on the agenda for year two, once the product team has a list of what it would build.

• Rebuild if your product is genuinely unlike a remittance platform, you already employ a strong engineering team, and you can afford a long period of running two systems.
• White label if your problem is an ageing or unsupported platform, slow corridor launches or compliance and finance work done outside the system, and your advantage is in pricing, corridors and service rather than software.
• Own the source code if you want to build on top of the platform, need the assurance of holding the code, and have, or will hire, engineers to own it.

For how volume growth changes the picture, see scaling from 10,000 to 100,000 transfers. For the cost of running several tools instead of one, see patchwork versus one platform.

RemitSo is a white label remittance platform with optional source code ownership. For operators moving off an ageing system, see the enterprise page.

• Published pricing: $7,999 setup and a monthly fee by completed transfers, so the three-year cost can be modelled before you talk to anyone.
• No revenue share, and hosting in your own AWS account: you see the infrastructure bill directly.
• Engineering at $25 an hour, only for time logged: changes are paid for when you need them, not as a fixed retainer.
• Source code at $77,999 once or $20,000 a year for five years: control when the business is ready to build on top.
• A staged migration: RemitSo migrates your data, you trial it, then launch with a focused group of customers before moving the rest.
• 100+ corridors and 50+ connections: a new corridor is a setting, not a project.
• Compliance and accounting in the platform: 8 sanctions lists reloaded nightly, 46 risk indicators, and a double-entry engine that records every money movement.
• A 99.99% uptime SLA, with releases tested on your staging first, and ISO 27001:2022 and ISO 9001:2015 certification.

Your team still negotiates partner contracts, sets corridors, fees, rates and compliance rules, runs the trial and decides when customers move. Compare the admin tools on the features page.