Short answer: The cost of running a money transfer platform is driven less by the software than by what happens around every transfer: the people who review and decide, the checks on every new customer, the fees to collect and pay out money, the cash tied up prefunding partners, and the effort of every change. Software choices matter because they decide how much of that work needs a person, and how much each change costs.
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 or financial advice.
Fixed costs and costs that grow with volume
Split every line in your model into one of two groups:
- Largely fixed: licence upkeep, your compliance officer and core team, audits, banking relationships, and the base cost of your platform.
- Grows with activity: identity checks (with new customers), payment and payout fees (with transfers), screening and review workload (with transfers and names), prefunding (with the amounts you send), and support (with customers).
A model that treats everything as fixed will look fine at launch and break as volume grows. A model that treats everything as variable will understate what you need before the first transfer.
1. Compliance and operations people
For most licensed operators, people are the largest cost. Your compliance officer, reviewers and operations staff spend their day on what the platform puts in front of them. The driver to watch is how many items need a person. If clean transfers flow on and only flagged ones wait, your team spends its time on decisions. If everything lands in a manual queue, headcount grows with volume. Training is a recurring cost too; see managing recurring compliance training.
2. Identity checks for every new customer
Electronic identity checks are usually charged per check by the identity provider, so this line grows with sign-ups, including sign-ups that never send. Manual document review costs staff time instead. Two levers keep it down: checking identity at the point a customer is ready to send, and asking for more documents only when amounts grow. On RemitSo, e-KYC and manual KYC are both part of the platform; the identity provider behind e-KYC is under your own contract and bills you directly.
3. Screening and monitoring workload
The cost here is rarely the screening itself; it is the review load it creates. Common and repeated names can produce many possible matches, each needing a person. Ask how matches are presented, how quickly a reviewer can rule, and whether everything is kept on record. Our guide to sanctions screening for remittance companies covers the trade-offs.
4. Collecting payments
Every way a customer pays (bank transfer, card and others) has its own fee and its own failure rate. Card collection is usually dearer than bank transfer; failed and reversed payments cost staff time as well as fees. Track each method's real cost per completed transfer, not its headline rate.
5. Paying out, and the cost of prefunding
Payout partners charge per payout, and the real cost often differs from the headline rate once failures, retries and manual handling are counted. Many partners also need prefunding, which ties up cash that could be working elsewhere. Our guides to corridor margin vs volume and liquidity planning by sender type go into landed payout cost and float in detail.
6. Banking
Business accounts for money transfer businesses come with fees, reserve or balance expectations and periodic reviews. The bank will ask about your controls and your technology provider, so the time spent answering is a cost too.
7. Hosting
Hosting grows with load, and with how many environments you run (production, staging, backups). Ask who pays it and whether it is marked up. On RemitSo, each operator runs in its own AWS account, and AWS bills the operator directly.
8. The platform itself
How you get the platform sets the shape of this line:
- Build: salaries for developers, QA and compliance support during the build, then ongoing fixes.
- Shared SaaS: subscription and usage charges, sometimes with a revenue share.
- White label: setup and platform fees, plus engineering time for changes beyond configuration.
- Owning the code: a transfer, then your own team for hosting, uptime and updates.
Our comparison of build, white label and SaaS explains the trade-offs. The build vs white label calculator compares a build with a white label on your own salaries, timeline and corridors over three years.
9. Change: corridors, rates and releases
Every business change has a cost: a new corridor, a new payout method, a new fee rule, a regulatory change. The driver is whether that change is configuration or a software project. If adding a corridor needs developers, every expansion carries a build cost. The same applies to upgrades: if an upgrade takes the whole platform down, it costs transfers as well as engineering time.
10. Audits and security reviews
Regulatory audits, bank reviews and payout partner due diligence all take staff time, and sometimes outside help. The cost falls when evidence is ready: audit trails that explain themselves, exportable reports and a list of every software component. See preparing for your first regulatory audit and passing a bank or partner security review.
11. Moving platforms
Switching has its own cost: data migration, a trial run, staff time and the risk of losing customers during the move. A staged move, with a small group first, keeps that risk contained. See migrating without losing customers.
How the drivers differ in Australia, Canada and on the Bangladesh corridor
- Australia: reporting to AUSTRAC is a recurring workload; the cost falls when report data is built from your transfers rather than a spreadsheet. See Australian money transfer rules.
- Canada: your obligations to FINTRAC shape your compliance staffing and record-keeping. See money remittance in Canada.
- Bangladesh corridor: a competitive, high-volume corridor where name screening load, payout reconciliation and rate pressure drive cost. Bangladesh Bank sets the receiving-side rules; your home regulator still applies. See running the Bangladesh remittance corridor.
How to model it
- List every cost line above and mark it fixed or variable.
- Put a driver against each variable line: per new customer, per transfer, per amount sent.
- Model three years, at your expected volumes and at half of them.
- Model corridor by corridor; averages hide loss-making corridors.
- Compare platform paths on your own numbers in the build vs white label calculator.
Frequently asked questions
What are the biggest costs of running a money transfer business?
Usually people and money movement rather than software: compliance and operations staff, payment collection and payout fees, the cost of prefunding payout partners, and identity checks for every new customer. The platform matters because it decides how much of that work needs a person.
Which costs are fixed and which grow with volume?
Licence upkeep, core compliance staff, audits and the platform base are largely fixed. Identity checks grow with new customers; payment, payout and screening workload grow with transfers; prefunding grows with the amounts you send. Hosting sits in between and grows with load.
How do we compare building our own platform with white label?
Enter your own team salaries, build timeline, corridors and monthly costs into the build vs white label calculator. It compares the two over three years, year by year.
Does the platform choice change our compliance costs?
It changes how much of the work needs a person. If clean transfers flow on and only flagged ones wait for review, your team spends its time on decisions rather than queues. The obligations themselves are set by your regulator and stay with you.
Who pays for hosting?
It depends on the vendor, so ask whether hosting is included, passed through or marked up. On RemitSo, each operator runs its own instance in its own AWS account, and AWS bills the operator directly. Hosting is not on your RemitSo invoice.
Where can we see RemitSo's own pricing?
RemitSo's published pricing is one setup fee of USD 7,999, a monthly platform fee from USD 299 set by the transfers you complete, and support at USD 25 an hour, billed only for time logged, with no revenue share. Hosting is billed by AWS to your own account. See the pricing page for the full tiers, and the build vs white label calculator to compare on your own figures.
Run your figures through the build vs white label calculator, then book a demo to see which of these costs the platform takes off your team.
Costs, fees and rules vary by market and change over time. Treat this as a guide to cost drivers, not financial or legal advice. Check with your compliance adviser.