Migration & Modernisation

How to Choose Remittance Software for Licensed Operators in the UK, Australia and Canada

A licensed money transfer operator does not choose software the way a start-up does. You already have customers, corridors, payout partners, a compliance programme and a regulator in your market. The question is not whether a platform can send money. It is whether it can carry the business you already run, in the United Kingdom, Australia or Canada, and give your team the records those regulators will ask to see.

This guide is for the people running that selection. It sets out what to write down before the first demo, what is different in each of those three markets, the criteria to weight, and a list of questions you can put to any vendor, including RemitSo. Where RemitSo is relevant we say so; everywhere else, the point is the question, not the brand.

Before you start

Write these down before anyone presents, then keep them in view when you score the criteria below.

  • Your corridors and payout methods: every sending country and every receiving country, and whether each pays out to bank accounts, cash pickup or mobile wallets.
  • Your compliance programme: the lists you screen against, the risk rules and limits you use, the documents you collect, and the reports your regulator expects.
  • The three problems that cost you most time or risk on the current system. These are what the new platform must fix, not just match.
  • Whether the books are a ledger your auditor will accept, with reversals rather than silent edits.
  • How the team is alerted when something needs a person, before the customer has to call.
  • What security evidence you can open and read, including certifications and who can see what.
  • A written split of responsibilities, and an exit path for your data if you leave.
  • How releases reach your staging environment before they reach live.

Turn the first three into a short list of test cases to run in each shortlisted vendor's staging environment, with your own (anonymised) examples, not the vendor's script.

What is different in the UK, Australia and Canada

The tooling you need is similar in all three markets: screening, monitoring, an audit trail, and reports built from the same transfer record. What changes is who you answer to, and which reports your team has to lodge. Software does not hold the licence and does not make you compliant. It either lets your team run the programme, or it forces workarounds.

Check with your compliance adviser before you treat any of the notes below as a requirement for your firm. Rules and thresholds change, and the right permission depends on what you actually do.

United Kingdom — FCA and HMRC

Money remittance is a payment service under the Payment Services Regulations 2017. A firm that provides it by way of business generally needs to be authorised by the Financial Conduct Authority as an authorised payment institution, or registered as a small payment institution, unless an exemption applies (FCA, Payment Services Regulations; FCA, payment institution applicants, which also sets out the conditions for registration as a small payment institution).

Money transmitters that only provide payment services as an authorised or small payment institution are generally supervised by HMRC under the Money Laundering Regulations, and authorised or registered by the FCA under the Payment Services Regulations. If a firm is also authorised by the FCA under the Financial Services and Markets Act, the FCA may be the anti-money-laundering supervisor (GOV.UK, who needs to register; HMRC, money service business supervision).

For the software, that usually comes down to a few practical questions. Can your team export a complete record of customers, transfers, screening decisions and rule changes for a review? Can they change a monitoring rule or a limit without waiting on a developer? Can they show where customer data is held, and who can see it?

Check with your compliance adviser.

Australia — AUSTRAC

To provide remittance services in Australia you must enrol with AUSTRAC and then apply for registration as a remittance service provider. You cannot provide remittance services until AUSTRAC approves the registration (AUSTRAC, register as a remittance or virtual asset service provider; AUSTRAC, remittance service providers overview).

Once you are registered, your team is responsible for the programme and for the reports that apply to your activity, including international funds transfer reporting where it is required. The useful software test is whether you can produce a complete, timely extract from the platform's own transfer record, and whether existing customers are re-screened when lists change.

Obligations change. Before you treat any note on this page as settled, read AUSTRAC's current guidance for remittance service providers.

Check with your compliance adviser.

Canada — FINTRAC

A business that offers money services in Canada generally needs to register with the Financial Transactions and Reports Analysis Centre of Canada (FINTRAC) as a money services business, and then meet the record-keeping and reporting duties that apply to it (FINTRAC, register a money services business; FINTRAC, check whether you need to register). Payment service providers may also need to register with the Bank of Canada under the Retail Payment Activities Act (Bank of Canada, registry of payment service providers), and Quebec licenses money services businesses separately through Revenu Québec (Money-Services Business Licence Application).

Ask any vendor whether you can produce those records from the platform, whether a person has to rule on a screening hit, and whether the reason for that decision is kept. Your team lodges the reports. The vendor does not.

Check with your compliance adviser.

Weight the criteria before you score anyone

Agree the weights before any vendor is scored. Weights set after the demos drift towards whichever vendor the room liked. Adjust the starting point below to your own risks, and keep the total at 100.

Criterion (example weight)What good looks likeQuestions to askRed flags
Compliance tooling (20)Every sender and recipient is screened; your team can change risk rules and limits; regulator reports are built from transfer dataShow a screening hit from alert to decision. Can we change a rule without a developer?Rules only the vendor can change; a possible match that blocks with no human decision; reports assembled by hand
Payout partner integrations (15)You hold the partner contracts; the platform connects and tests them; failures and bank recalls are flagged as they happenDo we hold our own partner contracts? What happens when a payout fails, and whose side was the fault on?"Operations sorts it out manually"; payout details editable after approval
White-label branding (10)Your name on the iOS, Android and web apps, on every screen the customer seesIs any vendor name still visible to the customer?A "white label" that still shows the vendor in the app stores or on receipts
Hosting in an account you own (15)A dedicated instance in a cloud account you hold and pay for, in a region you chooseWho holds the hosting account, who pays, and where does the data sit?A shared database in an unstated region; hosting bundled so you cannot see the bill
Source-code option (10)A documented route to owning the code, so you are not tied to the vendor's roadmapWhat exactly do we receive, and what does handover look like?No exit other than a data export
Support (10)Written hours, a named way to raise work, and a charging basis you can check against a logWhat are your hours, and how is support charged and evidenced?Support that is "included" until you need it, with no written hours
Pricing model (10)Published, and modelled on your numbers at today's volume and at twice it; hosting and third-party costs visible and separateWhat do we pay at today's volume and at twice that? Who pays for hosting?A share of your revenue or margin; corridor activation fees that only appear later
Migration support (10)A described process: who moves the data, how you trial it, how customers move across in stagesWho migrates our history? Can we trial it before customers see it?A single cutover as the only option

Score each criterion from 0 to 5 against your test cases, multiply by the weight and divide by 5. A perfect platform scores 100. For most licensed operators, a low score on compliance tooling or on a ledger your auditor will accept should end the evaluation, regardless of the total.

The questions to ask any vendor

Take this list into every demo and score each vendor against the same questions.

  • Responsibilities. What do you answer for, and what stays with us? A good answer is a written split. The vendor never claims to hold your licence.
  • Hosting and data. Where does our data live, and who else shares it? You want your own environment, in a region you choose.
  • Exit. What happens to our data and the platform if we leave? Your data should be portable. A source-code option is the stronger form of independence.
  • Screening. Who is screened, and when are they re-screened? Senders, recipients and, where relevant, staff, including when lists change.
  • Monitoring. Can we build our own rules and limits, including per corridor, without a code change?
  • Decisions. Does anything block a customer without a person deciding? A person should rule on every match and hold, and the reason should be kept.
  • Reports. Which regulator reports can we export for the UK, Australia or Canada? Named formats for your market; your team lodges them.
  • Partners. Do we hold our own payout-partner contracts? The vendor should connect and test them, not take them over.
  • Corridors. How is a new corridor added? Configuration, not a project.
  • Books. Is every payment, payout, refund, fee and FX movement booked as it happens? Double-entry, with reversals rather than silent edits.
  • Customer app. Is our brand on iOS, Android and web, on every screen?
  • Security evidence. Which certifications can we open and read? Fine-grained permissions and a sign-in record matter more than a logo on a slide.
  • Releases. Are updates tested on our staging environment first?
  • Migration. What does a staged move look like? Data first, a trial run, then customers in groups.
  • Commercials. What does it cost at our volumes? Ask every vendor to model it on your numbers and to show you published figures, not a slide. Ask who pays for hosting and whether anything is a share of your revenue.

Follow one transfer through to the books

Follow one transfer from the customer's payment, through the payout, to the ledger. Then break it on purpose.

  1. Underpay. Send a deposit that differs from what the customer declared. A well-designed platform holds it rather than guessing.
  2. Pay twice. Does the platform flag the duplicate the moment it lands, and how is the refund recorded?
  3. Fail a payout. Does the alert say whose side the fault was on, and whether the partner must be asked before a retry?
  4. Close the month. Ask finance to open the ledger and trace one partner balance back to its transactions. If they cannot, month-end will stay in spreadsheets.

If entries can be edited, or if fees and foreign exchange sit in one combined figure, the demo has not shown you a ledger your auditor will accept.

How to use the scores

Two or three vendors on a shortlist is usually enough. Weight the areas before you see anyone. Keep the evidence behind each score. The output should not only be a winner; it should be a short list of conditions to put in the contract, such as a written plan for moving a non-standard document archive, or a named report your team must be able to export in the trial run.

How RemitSo fits this list

RemitSo is white-label remittance software for licensed money transfer operators. It is a technology vendor, not a licensed money transfer business. Score it against your test cases like any other vendor.

What to verify, from RemitSo's own pages:

  • The software runs in your own AWS account, and AWS bills you directly. See pricing.
  • You keep your licence, your compliance decisions and your payout-partner contracts. The admin panel is there so your team can screen, monitor, decide and export evidence; it does not replace your compliance officer or your programme.
  • Branding covers the iOS, Android and web apps the customer uses, in your brand.
  • Pricing is published, the platform fee follows completed transfers, there is no revenue share, and support is billed hourly. Read the current figures on pricing and source-code pricing. There is a source-code option if you want to own the code.
  • On migration, RemitSo migrates the data and your team signs off each wave. You run a trial, then a focused launch, then everyone. You decide whether to run a parallel run alongside. Timing is agreed at kick-off.

See the enterprise page, or book a demo and bring your test cases.

Frequently asked questions

Does buying remittance software make us compliant?

No. Software can screen, monitor, flag and keep evidence. Your programme, your risk assessment and your decisions stay with your business and your compliance officer. Check with your compliance adviser.

How do the UK, Australia and Canada differ for the software itself?

The core tooling is similar. What changes is which regulator you answer to, and which reports your team must be able to export and lodge. Ask each vendor to show those reports for your market, built from the platform's own records. Check with your compliance adviser.

Where should our data live?

In an environment that belongs to you, in a region you choose, not in a shared database with other operators. On RemitSo, each operator runs the software in their own AWS account, and AWS bills that account directly.

Is a share of revenue a good pricing model?

It can suit a business that is only testing a market. For an established operator with steady volumes, a fee that follows completed transfers, with no share of revenue, is usually easier to model as you grow. Compare both on your own numbers, and read any published pricing rather than a slide.

Why does a source-code option matter?

It gives you a route off the vendor's roadmap, and a fallback if the vendor stops trading. Weigh it against the engineering needed to run and change the code. RemitSo publishes this option on source-code pricing.

Should the vendor hold our payout-partner contracts?

No. You should hold your own partner relationships. The vendor's job is to connect, test and show you what happened when a payout fails.

What should we ask to see in a demo?

A real audit-trail entry for a limit change, a sanctions match being ruled on by a person, one transfer followed from payment to payout to the ledger, and how a release reaches your staging environment.

Built by people who have helped MSBs for years.

47 ready-made risk indicators, drawn from what they see every day, combined into your own rules.

  • 47 ready-made risk indicators
  • Your own rules
  • 8 sanctions lists
  • A person decides
Book a demo

See RemitSo running with your corridors.

  • 30 minutes with our team, on video
  • The real admin panel and customer apps
  • The right way to buy it for you, explained with pricing
  • Your compliance and launch questions answered

We use these details to arrange your demo and reply to you. See our Privacy policy.

Loading the form…

Video