Why Established Money Transfer Operators Choose RemitSo

An established operator does not need persuading that software matters. It needs to know whether a move will leave the business better run a year later, and what the move will ask of its team. This page makes the case for RemitSo in those terms, ties each claim to something the platform actually does, and says plainly where RemitSo is not the right answer.

It is written for founders, CTOs, compliance heads, operations leads and finance at operators who already have a licence, corridors and customers, and whose current platform has become slow, costly to change or unsupported. RemitSo is a white label remittance platform, run in your brand, with the option to buy the source code.

Many established operators run a core transfer system plus separate tools for screening, reconciliation, reporting and customer messages, joined by exports and people. Each join is a place where a figure can disagree with another, and where nobody owns the gap. See patchwork versus one platform for where those joins tend to fail.

RemitSo puts the customer apps, transfers, compliance, accounting and the admin panel in one system. Customers use iOS, Android and web apps in your brand. Your team sees every transaction live in one admin panel. Screening decisions, KYC decisions, ledger entries and alerts all refer to the same transfer, so when someone asks "what happened to this one?", there is one place to look.

Access follows the same logic. Roles are built from 89 separate access controls, each described in plain language, and staff sign in with two-step sign-in. Each person sees only what their role allows.

Compliance that sits outside the platform is compliance that runs behind it. In RemitSo, it is part of every transfer:

• Sanctions screening of every sender and recipient against 8 lists, reloaded every night. When lists change, everyone is re-screened, staff included. Rulings are kept per person, so a cleared name is not flagged again.
• 46 ready-made risk indicators that your compliance team combines into its own rules. Risky transfers wait for a person; everything else flows on its own.
• Limits counted per transfer, over 90 days and over a year, set per route; as a customer sends more, the platform asks for more documents.
• Identity checks inside the first transfer, with ID, selfie and live face check, and a reviewer override that keeps the reason.
• Regulator reports built from transfer data, with a check that nothing was left out. Australia's IFTI-E report is supported today.
• A compliance dashboard and staff training with sign-off (training is an optional add-on), where nobody signs off their own.

For more on how the screening side works, see sanctions screening for remittance companies.

A growing operator cannot keep adding people to watch screens. The answer is to have the platform tell the team what needs a person, and leave the rest alone.

RemitSo's Scout checks everything every 5 minutes and shows, in one place, what needs an operator: transfers and payouts needing action, payments where a provider has not answered, compliance decisions waiting, and system health, including partners failing calls and rate feeds that have stopped. Each group of figures is granted by role.

Alongside Scout, 43 alert events go to the people subscribed to them, written in plain language. "Payout not sent because of a fault on our side" says whose side the fault was on and whether the partner must be asked before retrying. Every outbound API call and incoming webhook is logged, and a failed webhook can be retried in one click.

Maintenance follows the same principle. You pause only what the work needs, and money in flight carries on.

In many operators, finance rebuilds the month from exports. RemitSo's double-entry engine records every payment, payout, refund, fee and FX movement in the accounts as it happens. Entries are never edited; mistakes are reversed and both stay visible. Click any balance to see the transactions behind it.

Deposits are matched to what the customer declared, to the cent. Anything unclear is held, and if the amount does not match, the money does not move. Chargebacks, bank recalls and double payments are flagged the moment they happen. Payouts are locked once approved and never edited. Reading the ledger and posting a manual journal are separate permissions, so finance can see everything while a named controller posts by hand.

For an established operator, the reason to move is usually growth the current platform is blocking. On RemitSo a new corridor is a setting, not a project. There are 100+ corridors ready to switch on and 50+ connections to payment, payout, identity check and other partners.

• Rates per corridor on one Exchange Rates page, uploaded or typed, or from a live hourly feed with your margin (an optional add-on), with amount bands and different rates by customer group, platform, payment route, payout method or partner. A feed rate that moves beyond your configured guardrail is not written; the feeder switches itself off and alerts its subscribers.
• Fees flat, percentage, minimum and maximum, by payment method and amount. No corridor goes live until its fees are set.
• Languages: English, French or Spanish, switched on with a translation dictionary you provide; emails go in the customer's own language.
• Wallets, an optional add-on, where your licence allows, with balances that cannot go below zero.

The fear that keeps operators on ageing platforms is the move itself. RemitSo's migration is staged to keep that risk small:

1. RemitSo migrates your data. Your team checks what arrives.
2. You run a trial. If you want extra assurance, you can also run your own parallel run alongside the old system, for as long as you decide.
3. You transfer in stages. Launch first with a new, focused group of customers, then migrate the rest.

Problems surface in a small group rather than across your whole book. Your old system keeps serving customers until they move. For the customer side of the move, see migrating without losing customers.

White label answers the immediate problem. Some operators later want to build things of their own on top: a new product line, an internal tool, a deeper integration with the rest of a group. RemitSo's source code is available for $77,999 once, or $20,000 a year for five years. It needs a team able to own it, which is why many operators treat it as a second step. See owning your remittance source code.

• You want someone else to run compliance. RemitSo is a platform. It does not hold your licence or make your compliance decisions.
• You need regulator reports RemitSo does not build yet. Australia's IFTI-E is supported today. If you depend on another format, check before you commit, or plan to produce it from exports.
• You need languages beyond English, French and Spanish in the customer apps today.
• You must host outside a dedicated AWS account, for example on your own premises or another cloud.
• Your product is not a remittance business at heart, and you would spend more effort changing the platform than using it.

The operator and all figures are illustrative, not drawn from any real business.

An operator in its tenth year runs seven corridors, about 3,000 completed transfers a month, on a platform its vendor no longer develops. Compliance clears screening matches in a separate tool and builds its regulator report by hand. Finance spends several days each month matching deposits.

They choose RemitSo white label. At 3,000 transfers a month, the published fee is $499 a month after a $7,999 setup. RemitSo migrates their data while the compliance lead rebuilds the risk rules from the 46 indicators and the finance lead agrees opening balances. During the trial, they choose to run their own parallel run on their two largest corridors.

For the first stage they pick a new, focused group: customers who joined in the past six months on one corridor. After a few weeks of watching those transfers through Scout and the alerts, they migrate everyone else. Two corridors the old vendor had quoted as projects are switched on as settings. The source code question goes to the board for next year.

For established operators moving off an ageing platform, start with the enterprise page.

• One platform for apps, transfers, compliance and accounting: one record of every transfer, live in one admin panel.
• Screening against 8 lists, reloaded nightly, and 46 risk indicators: risky transfers wait for a person; the rest flow.
• Scout and 43 plain-language alerts: the team works on what needs it.
• A double-entry engine and deposits matched to the cent: the books post themselves and every balance can be traced.
• 100+ corridors and 50+ connections: new corridors are settings, not projects.
• A staged migration: your data migrated, a trial on your terms, a focused first group, then everyone else.
• Published pricing with no revenue share: see the pricing page.
• Source code when you are ready: see source code pricing.

Your team still holds the licence, writes the rules, makes the compliance decisions, negotiates partners and runs the trial. See every admin tool on the features page.