Short answer: Building in-house gives you full control but leaves you running a software company alongside your money transfer business. Shared SaaS is the quickest start, but your data and release schedule sit alongside other operators'. A dedicated white label sits between the two: a platform that is yours alone, under your brand, kept current by the vendor. Whichever you choose, the licence and every compliance decision stay with you.
RemitSo is white-label remittance software for licensed money transfer operators. We are a technology company, not a money transfer business, and nothing here is legal advice.
Who this guide is for
Owners, compliance heads and operations leads at licensed or soon-to-be-licensed money transfer operators who have to choose a platform and defend the choice to a board, a bank or a regulator. If you already run a platform and are weighing a move, the true costs of rebuilding, moving to white label or owning the code is written for you.
The three approaches, defined
Build in-house. Your own team designs, builds and runs the customer apps, the admin panel, the payment and payout connections, compliance tooling and the books. You own everything, and you maintain everything.
Shared SaaS. You subscribe to a platform that many operators use at once. The vendor runs one system and one release schedule; you configure your part of it.
Dedicated white label. You get a platform of your own, under your brand, which the vendor builds, hosts or manages, and updates. Some vendors also let you take the source code later.
What changes for your licence and your regulator
Nothing changes about your obligations. Regulators such as AUSTRAC in Australia and FINTRAC in Canada look to the licensed business for its controls, whoever wrote the software. What changes is how easily you can show those controls: who screened whom, which rule held a transfer, who decided and why.
So ask of every approach: will we be able to produce that evidence on the day an examiner asks? Our guide to preparing for your first regulatory audit covers what that pack usually contains.
Control: who decides what changes, and when
Control is the clearest difference between the three, and it cuts both ways.
- Build: you decide everything, including priorities, and you carry every change yourself, from a new corridor to a new sanctions list format.
- Shared SaaS: the vendor decides when releases ship, for everyone at once. You get updates without effort, but on the vendor's timetable.
- Dedicated white label: the vendor ships updates, but to your platform alone. Ask for every release to reach your staging environment first, so your team checks it before production. On RemitSo, every release goes to your staging first, and each release says whether it needs downtime.
Data and hosting: where customer records live
"Where is our data, and who else is on that server?" is one of the first questions a bank partner or auditor will ask, so settle it before you choose.
- Build: wherever you put it, which also means you run the security, backups and monitoring.
- Shared SaaS: usually in the vendor's environment, alongside other operators' data. Ask how it is separated.
- Dedicated white label: it depends on the vendor. On RemitSo, each operator runs its own instance in its own AWS account, in the AWS region it chooses. AWS bills the operator directly, and nothing is shared with another operator.
Compliance evidence: what you can show an examiner
Whatever you choose, the platform has to let you prove five things:
- Screening of every sender, recipient and staff member, with re-screening when lists change.
- Monitoring rules and limits you set yourself, per currency and corridor.
- A person on your team ruling on every match and every held transfer, with the reason kept.
- Audit trails that say what changed, from what, to what, and who did it.
- Reports you can export, with your team reviewing and lodging them.
Building all of this in-house is possible, but it is the part that never finishes. Shared SaaS and white label both arrive with it; the question is whether it fits your rules and your regulator.
Time and effort before your first transfer
A build is the slowest route, shared SaaS the fastest, and a dedicated white label sits close to SaaS. A build has to deliver apps on iOS, Android and web, an admin panel, payment collection, payouts, identity checks, screening, monitoring, accounting and notifications before the first customer sends. Shared SaaS is quickest because the platform already exists. On RemitSo, the launch timeline is agreed at kick-off and depends on your corridors, partners and approvals.
In every case, the licence sets the real pace. Our platform and operations checklist shows what has to be ready before go-live.
What drives cost over three years
The approaches differ less in the first invoice than in what keeps costing money afterwards:
- Build: salaries for developers, QA and compliance support; ongoing fixes; every new corridor and regulatory change as a project.
- Shared SaaS: subscription and usage charges; any revenue share; the cost of working around features you can't change.
- Dedicated white label: setup and platform fees; hosting; any add-ons and engineering time for changes beyond configuration.
Every approach also carries costs that sit outside the software: identity checks per customer, payment and payout fees, banking, compliance staff and audits. Our guide to what drives the cost of running a money transfer platform lists them. To compare a build with a white label on your own numbers, use the build vs white label calculator. If you already run a platform, the true costs of rebuilding, moving to white label or owning the code is the better starting point.
Side by side
| Question | Build in-house | Shared SaaS | Dedicated white label |
|---|---|---|---|
| Who owns the code? | You | Vendor | Vendor, with some offering a code transfer |
| Where does data live? | Where you host it | Usually the vendor's shared environment | Depends on vendor; on RemitSo, your own AWS account |
| Who ships updates? | Your team | Vendor, same schedule for all | Vendor, to your platform; ask for staging first |
| Brand on the apps | Yours | Often yours, within limits | Yours, on every screen |
| Compliance tooling | You build it | Included; fit varies | Included; check it matches your rules |
| Time to first transfer | Longest | Shortest | Close to SaaS |
| Ongoing effort | Highest | Lowest | Low |
| Licence and decisions | Always yours | Always yours | Always yours |
Which approach fits which operator
- A newly licensed operator in Australia with a small team usually wants to spend its effort on banking, partners and AUSTRAC obligations, not software. A dedicated white label fits, provided the data sits in an environment it controls. See launching a money transfer business in Australia.
- A Canadian operator adding a Bangladesh corridor needs corridors that are a setting, not a project, and screening that copes with the name load on that corridor. See running the Bangladesh remittance corridor and money remittance in Canada.
- A bank, credit union or larger operator with its own engineering team may want to own and extend the code. Our guide to owning your remittance source code covers what that takes on.
- An established operator on an ageing platform should weigh the move itself as much as the destination. Start with the ten-question migration check.
Where RemitSo fits
RemitSo is a dedicated white label: your own instance, your branded iOS, Android and web apps, and one admin panel for compliance, rates, payouts and your books, run and updated by us. If you want to own it outright, the complete source code can be transferred to you after a live code audit. Either way, it runs in your own AWS account, the compliance tools flag and your team decides, and RemitSo is ISO 27001:2022 and ISO 9001:2015 certified.
Frequently asked questions
What is the difference between white label and SaaS remittance software?
Both are software you don't build yourself. Shared SaaS usually runs many operators on one platform, with one release schedule for everyone. A dedicated white label gives one operator its own platform under its own brand, kept current by the vendor. On RemitSo, each operator runs its own instance in its own AWS account, and nothing is shared with another operator.
Is it cheaper to build remittance software in-house?
Rarely in the first years. The build is the smaller part; the larger part is the work that never ends: compliance updates, payout partner changes, security reviews, accounting and support. Put your own team costs and timeline into the build vs white label calculator and compare three years, not one.
Do we still need our own licence with white label or SaaS?
Yes. Whichever approach you choose, the licence and the compliance decisions stay with the licensed business. RemitSo is a technology company, not a licensed money transfer business.
Can we start on white label and own the code later?
With RemitSo, yes. There are two routes: a white label run and updated by us, or the source code transferred to you after a live code audit. If you take the code, hosting, uptime and updates become yours.
How long does each approach take to launch?
A build takes longest, because every part has to exist before the first transfer. Shared SaaS is usually quickest, because the platform already exists. A dedicated white label sits close to SaaS; on RemitSo, the launch timeline is agreed at kick-off and depends on your corridors, partners and approvals. In every case, the licence sets the real pace.
Which approach do regulators prefer?
Regulators look at the licensed business's controls, not at how the software was sourced. What matters is whether you can show your screening, monitoring, decisions and records. Check what your regulator expects, starting with AUSTRAC in Australia or FINTRAC in Canada.
Compare a build with launching on RemitSo in the build vs white label calculator, then book a demo to see it running with your corridors.
Rules differ by market and change over time. Treat this as a guide to choosing a platform, not legal advice. Check with your compliance adviser.