Short answer: A money transfer business starts with a licence or registration in each country it sends from, a bank that will hold its accounts, payout partners in each country it sends to, and a compliance programme its regulator will accept. The platform comes after those decisions, but it has to evidence every one of them from the first transfer. This guide is the checklist we'd use, with links to our country guides for the regulator-specific detail.
RemitSo is white-label remittance software for licensed money transfer operators. We are a technology company, not a remitter, and nothing here is legal advice.
Step 1: The licence comes first, and it shapes everything else
Every market has its own regulator, its own route and its own timeline. The licence decides which customers you can serve, which reports you file, which records you keep and what your platform must evidence. Start with the regulator's own pages, then our guides:
| Market | Regulator | Our guide |
|---|---|---|
| Australia | AUSTRAC | Australian Money Transfer Rules 2026 and Launching a Money Transfer Business in Australia |
| Canada | FINTRAC | Money Remittance in Canada |
| United States | FinCEN and state regulators | Money Transmitter Licenses in the US and FinCEN MSB registrant search |
| United Kingdom | FCA | API, SPI or EMI: What Each FCA Route Means for Your Remittance Platform |
Corridor guide: Running the Bangladesh Remittance Corridor.
What it means for your platform: list your corridors, your partners and your technology provider exactly as your application describes them. A regulator compares what you said with what you run.
Step 2: Banking, and where customer money sits
Banks are often the hardest part of launching. A bank will ask how you screen customers, how you monitor transfers, how you reconcile and who your technology provider is, much as a regulator would. Our guides on opening a business bank account for a UK money service business and a US money transfer company cover the questions to expect.
What it means for your platform:
- Books from day one. On RemitSo, a double-entry ledger records every payment, payout, refund, fee and FX movement as it happens, and revenue is booked only when the recipient is paid.
- A security file you can hand over. RemitSo is ISO 27001:2022 certified, and the admin panel lists every deployed software component with its version and licence, so your bank's security review has the list, not a promise.
Step 3: Payout partners for every corridor
Each country you send to needs at least one partner that can pay recipients by bank deposit, mobile wallet or cash pickup. Our guide to choosing and running payout partners covers coverage, prefunding and failure handling.
What it means for your platform:
- Your contracts, connected for you. You hold the contract with each payment and payout partner, so the commercial terms are yours. RemitSo connects and tests them.
- Three ways to pay out. Bank deposit, mobile wallet and cash pickup are supported.
- Corridors as settings. Payout channels, banks and onboarding fields are set up by configuration, so a new corridor is a configuration task, not a software project.
- Payouts that can't be redirected. Once a payout is approved, nobody can change it.
Step 4: Compliance controls your regulator will recognise
Your AML programme, your risk assessment and your officers' judgement are yours. The platform should mirror them, enforce them and keep the evidence.
- Know your customer. e-KYC through a connected identity provider (ID document, selfie and live face check), manual document review, or both. A reviewer can overrule a check, and the reason is kept.
- Limits that ask for more. "Up to" limits per transaction and over a day, week, month, 90 days or a year, per currency and corridor, with documents named for each tier.
- Sanctions screening. Eight sanctions lists, kept up to date. Every sender, recipient and staff member is screened, and everyone is re-screened when the lists change. A possible match holds the transfer until an officer rules on it.
- Monitoring. Rules built from 47 ready-made risk indicators. Clean transfers flow on, and the rest wait for a person.
- Training. An optional add-on assigns staff courses, sends reminders and keeps a permanent record.
The rule we design to is simple: the platform flags, and your compliance team decides.
Step 5: Choose how to own the platform
There are three broad ways to get a platform: build it, license a white-label platform, or buy source code. Each has a different cost profile, timeline and level of control. Our guides to white-label money transfer software and build vs white label compare them.
Questions to ask any vendor:
- Where does our data live, and who pays for hosting? 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.
- Who holds the licence? RemitSo holds no money transfer licence and doesn't act as one. The licence is yours.
- How do updates reach us? Ask for every release to reach a staging environment first, so your team can check it before it reaches production.
- What can our auditors see? Clear audit trails, user access logs, roles for every page and action, two-step sign-in and exportable compliance reports.
Step 6: Price your corridors, then check the books agree
Before launch, set exchange rates, fees and limits per corridor, and decide who can change them.
On RemitSo, you can type rates or import them, give larger transfers a better rate tier by tier, and set flat, percentage, minimum or maximum fees per corridor with a review reminder. No corridor goes live until its fees are set, even if they're zero. Every change records who made it, when, and what it was before. Bank fees, partner fees and discounts each have their own account, so real margin is visible.
Step 7: Launch in stages
A careful launch tests every corridor end to end before customers see it, and moves volume across gradually.
- Before go-live: your own instance, your branded iOS, Android and web apps submitted to both stores, the admin panel, and your corridors, partners and compliance rules. Ask any vendor for a dated plan, and build it around your licence, not the other way round.
- If you're moving from another platform: we move your data and history first, you run a trial, then customers move in groups, so nobody switches overnight. Our data migration checklist covers what to check.
Step 8: Run it like an examiner is watching
Your first regulatory audit will ask what you did, not what you intended. Our guide to preparing for your first regulatory audit covers the evidence pack. Day to day, three habits make audits routine:
- Reconcile daily. Match money in, money out and money held. The platform should flag differences; a person should explain them.
- Decide and record. Every hold, match and raised limit gets a decision and a reason, kept with the record.
- Keep the configuration honest. Rules, limits and document tiers in the system should match your written policies, and each change should be logged.
The checklist
| Area | What should be in place before launch |
|---|---|
| Licence | Licence or registration in each sending country; corridors and partners match your application |
| Banking | Business accounts open; your bank's security and compliance questions answered |
| Payout partners | Contracts signed, connections tested end to end, failure handling agreed |
| Compliance controls | KYC, limits, sanctions screening and monitoring rules matching your policies |
| Platform | Your own environment, data location known, releases tested on staging |
| Pricing | Rates, fees and limits set per corridor, with change history |
| Books | A double-entry ledger, with partner and bank fees in their own accounts |
| Audit evidence | Audit trails, user access logs and exportable compliance reports |
Frequently asked questions
Do we need our own licence to use RemitSo?
Yes. RemitSo is the technology; the licence to move money is yours. Our country guides link to each regulator's own pages.
Which comes first, the licence or the platform?
The licence application usually needs a clear description of your systems and controls, so choose your platform while you prepare it. Go live only once the licence is granted.
What has to be ready before go-live?
Your own instance, your branded apps, the admin panel, and your corridors, partners and compliance rules, all tested end to end. The timing depends on your licence, your partners and your own sign-off.
Do we sign our own partner agreements?
Yes. You hold the contract with each payment and payout partner, so the commercial terms are yours. RemitSo connects and tests them.
Where is our customer data held?
In your own instance, in your own AWS account, in the AWS region you choose. AWS bills you directly, and nothing is shared with another operator.
For more, see what RemitSo handles and what stays with you, the getting started guide and our KYC, AML and sanctions tools. Book a demo to walk through this checklist with your own corridors.
Rules change, and each regulator's own pages are the authority. Treat this as a guide to what your platform and operations should evidence, not as legal advice. Check with your compliance adviser.