Is It Time To Move? Check, Then See How
For established money transfer operators. Ten questions about an ordinary week show how much your team does by hand. Then the four stages of a move, and who does what.
Ten signs your platform is costing you more than you think.
Answer yes or no. Each yes shows how the same task works on RemitSo.
Does someone check or update exchange rates by hand every day?
On RemitSoThe admin panel says when a rate has not moved, and names the currency pair. See how RemitSo handles question 1 →
Does a person, not the system, remember when fees, rates and lists are due for review?
On RemitSo43 alert events. A reminder repeats once a day until the job is done. See how RemitSo handles question 2 →
Would you have to ask someone to know when your sanctions lists last updated?
On RemitSoEight lists load every night, and the panel says if one is out of date. See how RemitSo handles question 3 →
When a customer wants to send more, does someone look up their totals by hand?
On RemitSoLimits by transaction, day, week, month, 90 days or year. Each tier names its documents. See how RemitSo handles question 4 →
Does month end start with looking for a difference?
On RemitSoDeposits are matched to the cent, and every movement is in the ledger as it happens. See how RemitSo handles question 5 →
Does answering “who changed that?” take more than a search?
On RemitSoA plain-language audit log you can search: who changed what, and when. See how RemitSo handles question 6 →
Do new staff learn the platform’s terms by asking colleagues?
On RemitSoA glossary inside the admin panel, with a link from each term to its page. See how RemitSo handles question 7 →
Do you usually hear about a failed payout from the customer first?
On RemitSoScout checks every five minutes, and alerts say whose side a fault is on. See how RemitSo handles question 8 →
Is a report to your regulator built in a spreadsheet each time?
On RemitSoThe report file is built from your transfers and checked against every one in scope. Available today for Australia’s IFTI-E. See how RemitSo handles question 9 →
Is adding a new corridor a project, not a setting?
On RemitSoPayout channels, banks and onboarding fields load from a file, with 100+ corridors ready to switch on. See how RemitSo handles question 10 →
Answer the ten questions to see where your week goes.
Each yes is a task your team does by hand that a platform can carry.
Your answers stay in this browser. Nothing is sent to us, and nobody will call you.
Four stages. Each ends with a test.
You do not move everyone on one date. A stage must pass its test before the next begins, and you stay in control of the pace.
-
RemitSo
Data migration
Customers, recipients, compliance records, history and settings move to your RemitSo platform.
- Live traffic on
- Old platform
- Test to pass
- Counts, totals and samples agree.
-
You
Trial run
Your staff run real tasks and test transfers end to end, on every corridor.
- Live traffic on
- Old platform
- Test to pass
- Every corridor, payment route and payout method works, including failures and refunds.
-
Together
Focused launch
A new, small group of customers starts on the new platform.
- Live traffic on
- New for the group, old for everyone else
- Test to pass
- The group transacts without unexplained issues.
-
Together
Mass migration
Everyone else moves, often in waves.
- Live traffic on
- New platform
- Test to pass
- The old platform carries no new transfers.
Optional, between stages 2 and 3: your own parallel run. You run both systems and compare the figures. The test is that every mismatch is explained and closed.
Our part, and yours.
What RemitSo does
- We migrate your data. Your team checks and signs it off; it does not build the extraction.
- Deposits are matched to the cent, and anything unclear is held, so a mismatch is visible.
- Payout channels validate recipient details, so a record that would fail is caught before a customer sends.
- Your brand on every app, with saved recipients carried across.
What stays with your team
- The trial script.
- Whether to run your own parallel run alongside.
- The go or no-go for each wave.
- What you tell customers, regulators, banks and partners.
- The ruling on each mismatch.
What moves, and who signs it off
- Customers and profiles
- Operations
- KYC documents and decisions
- Compliance
- Recipients and payout details
- Operations
- Transaction history and states
- Finance and operations
- Wallet balances, where licensed
- Finance
- Open transfers in flight
- Operations
- Ledger opening balances
- Finance
- Sanctions screening decisions
- Compliance
- AML rules and watched lists
- Compliance
- Rates and fees
- Treasury and finance
- Staff users and roles
- Compliance and technology
Three guides for the team planning the move.
The signs that it is time, and the signs that it is not.
Read the guide → Migrating without losing customersThe four stages in full: trial run, focused launch, then everyone.
Read the guide → The data migration checklistWhat to move, how to check it arrived, and who signs it off.
Read the checklist →A migration has an end date. The daily grind does not.
Built by people who have helped MSBs for years.
The risk checks on every online transfer come from what they see every day.
- The person paying isn't the customer
- One bank account, several customers
- A disposable email address
- Sign-in from a high-risk location
- The same person signing up twice
- A name close to a sanctions list