Customer App & Growth

Customer Wallets for Money Transfer Businesses: How to Launch Stored Value Safely

Licensing, verified identity, double-entry balances and deposit matching: what to settle before your customers hold money with you

A customer wallet changes the relationship between a money transfer business and its senders. Instead of paying in for every transfer, the customer loads a balance once and sends from it many times. That convenience is real, but so is the responsibility: the moment a customer holds money with you, you are keeping stored value, and the questions about licensing, safeguarding, identity and accounting become sharper than they are for a simple pay-in, pay-out transfer.

This guide is for founders and compliance heads deciding whether, and how, to add wallets to a remittance service.

RemitSo is one way to run wallets. It provides them in the customer app as an optional add-on, where your licence allows, with balances drawn from your accounts and funding limited to verified customers. It does not decide whether you may offer stored value, design your safeguarding or write your policies; those stay with your team and advisers.

01 · WHY WALLETS

Why Wallets Bring Senders Back

Most remittance customers send regularly: a monthly contribution to family, school fees each term. Without a wallet, each transfer means a fresh bank payment to the operator that must arrive and be matched before anything moves. A wallet lets the customer load once, for example on payday, and send from the balance many times. Three things follow for the operator:

  • Faster repeat transfers. When funds are already held and matched, a transfer paid from the balance does not wait for an incoming bank payment.
  • A reason to come back. A visible balance is a quiet prompt to send through your app rather than shop around.
  • Fewer payment exceptions. One load for several transfers means fewer bank payments to reconcile and fewer mistyped references.

A wallet that is slow to update or occasionally wrong does more damage to trust than having no wallet at all, so the foundations matter.

Takeaway: a wallet is a retention feature built on a regulated obligation. Treat it as both from the first planning meeting.

02 · LICENSING FIRST

What to Check Before You Hold Customer Balances

Whether you can offer a wallet at all depends on where you are licensed and what your licence permits. A licence that covers money remittance does not necessarily cover holding funds for customers. This is not legal advice; these are the questions your compliance lead and advisers should answer before any build work starts.

Questions about permission

  • Does our current licence or registration allow us to hold customer funds that are not tied to a specific transfer? Or does stored value require a different permission, such as an e-money authorisation, in our jurisdiction?
  • Are there limits on how long funds can be held before they must be sent or returned?
  • If we operate in more than one market, does each market need to be assessed separately? Usually the answer is yes.

Questions about safeguarding

  • How must customer funds be protected: segregated accounts, insurance or a guarantee, or another method recognised in our jurisdiction?
  • How often must we reconcile customer balances against the safeguarded funds, and who signs that reconciliation off?

Questions about customer terms

  • Can customers withdraw an unused balance, and on what terms?
  • How are dormant balances handled, and is interest prohibited?

Two of these answers should shape how the platform is set up. If permission differs by market, wallets should be switched on country by country, and each decision should be recorded with its date so you can show a regulator exactly when stored value became available where. If terms differ by market and language, each version a customer accepted has to be kept as it was. In RemitSo, switching wallets on or off for a country is a dated decision with its own history, and switching a country off never touches wallets that already exist there. Wallet terms are versioned per country and language; a published version is never edited, so the wording a customer agreed to is the wording you can produce later.

Warning: do not switch wallets on and resolve the licensing question afterwards. Unwinding customer balances is far harder than delaying a launch.

03 · IDENTITY

How to Require Verified Identity Before Funding

Many remittance apps run the full ID check during the first transfer rather than at sign-up, which reduces drop-off. A wallet needs a firmer line: no one should be able to put money into a balance until their identity is verified.

A balance loaded by an unverified customer is money you already hold for someone you cannot identify: a financial-crime risk, and an awkward question about how to return it if verification fails. In practice:

  1. Show unverified customers why they cannot load yet, rather than a load button.
  2. Let customers resume an unfinished ID check rather than starting again, so the requirement does not become a reason to leave.
  3. Run the same ID, selfie and live face check you use for transfers.
  4. Screen the customer against sanctions lists before the first load, not only before the first transfer.

In RemitSo, funding a wallet requires a verified identity, and customers can pick up an unfinished ID check where they left off. Sanctions screening covers every sender and recipient against 8 lists, reloaded every night, with everyone re-screened when the lists change.

04 · THE LEDGER

How Balances Must Come From the Books

The most common way for a wallet to go wrong is for the balance to be a number stored on its own rather than derived from the accounts. Sooner or later the two drift apart: a refund recorded in one place but not the other, or a manual correction to the balance but not the ledger. Then you no longer know what you owe each customer.

The safer design is that the balance is always the result of the accounting entries: a double-entry ledger in which every load, transfer, fee and refund is recorded as a debit and a matching credit.

Rules a wallet ledger should follow

  • Balances can never go below zero. A transfer that would take the balance negative is refused, not allowed through and chased later.
  • Entries are never edited. A mistake is corrected with a reversing entry, and both the original and the reversal stay visible.
  • Every balance can be explained. Anyone with the right permission should be able to open a customer's balance and see the transactions behind it.
  • Fees and discounts are kept separate. If a promotion reduced a fee, the discount sits in its own account so finance can see its cost.

RemitSo's admin panel includes a double-entry engine that records every payment, payout, refund, fee and FX movement automatically, with any balance clickable down to its transactions. Wallet balances come straight from those accounts, so finance and the customer see the same number.

05 · LOADING

How to Handle Loading by Bank Transfer and Matching Deposits

Bank transfer is inexpensive, but it puts the customer in charge of typing an amount and a reference into their own banking app, which is where most loading problems begin. A good loading flow works in two halves:

  1. The customer declares the load in the app first. They state the amount they intend to send and receive clear payment instructions, including who the payee is and the reference to use.
  2. The incoming payment is matched against that declaration. Only when the amount and reference match does the balance increase.

For a slightly different amount, a missing reference or two deposits for one declaration, the rule should be strict: if the deposit does not match, the money does not move. It is held for a person to review rather than credited on a best guess.

RemitSo matches deposits to the declaration to the cent and holds anything unclear. Named alerts go to the people subscribed to them: "Deposit received but matched nothing" for a load with no usable reference, "Duplicate payment captured" for two deposits against one declaration, and "Bank took money back" for a recalled load, so a reversed load does not quietly leave a balance overstated.

Operating note: decide in advance who reviews held deposits, how quickly, and what the customer is told while they wait. A held deposit with no message is the kind of thing that generates support tickets and complaints.

06 · STATEMENTS

What Customers Need to See: Live Balances and Statements

  • A live balance. The figure should update as soon as a load is matched or a transfer is paid from it. A balance that lags behind leads customers to think money has gone missing.
  • Statements on demand. For their own records or to show a bank or landlord, downloadable at any time.

A statement that agrees with the ledger finance uses also settles balance disputes quickly, so test that agreement before launch and sample it after. In RemitSo's customer app, customers see their wallet balance update live, download receipts and account statements any time, and can request statements.

07 · CONTROLS

How Wallets Interact With Limits and Screening

A wallet must not become a way around controls you already apply to transfers.

Limits

If your transfer limits are counted per transfer and over rolling periods, transfers paid from a wallet must count towards them in exactly the same way as transfers paid by bank transfer. Decide too whether loads need their own thresholds: a customer who loads far more than they send may deserve a question.

Screening and risk checks

Every transfer paid from a balance should go through the same sanctions screening and risk checks as any other. Watch for wallet-specific patterns: rapid loads followed by transfers to many new recipients, or loads from an account in a different name.

In RemitSo, limits are counted per transfer, over 90 days and over a year, per route and per app. You combine 47 ready-made risk indicators into your own rules; risky transfers wait for a person.

Pay-per-transfer compared with wallet-funded transfers
AreaPay per transferWallet-funded
LicensingCovered by a typical remittance permissionMay need additional permission; check by jurisdiction
IdentityVerified during the first transferVerified before any money is loaded
Funds heldBriefly, for a specific transferFor an open period, not tied to a transfer
ReconciliationOne incoming payment per transferOne load, many transfers; balances reconciled to safeguarded funds
Speed of repeat transfersWaits for each bank paymentPaid from a balance already matched
Limits and screeningApplied per transferApplied per transfer, plus a view on loading patterns
Customer recordsReceipts per transferReceipts plus balance statements
08 · SCENARIO

Scenario: One Load, Three Transfers and a Mismatched Deposit

The figures below are illustrative only.

A customer in the United Kingdom, verified three months ago, sends money home every few weeks. On payday she opens the app and declares a wallet load of GBP 600. The app shows her the payee, which is the operator's own brand, and the reference to use. She makes the bank transfer.

  1. Day 1, the load. A deposit of GBP 600.00 arrives with the correct reference. It matches her declaration to the penny. The ledger records the incoming funds and the matching credit to her wallet; her balance shows GBP 600.00.
  2. Day 3, first transfer. She sends GBP 250 plus a GBP 2.99 fee from the wallet. Screening and risk checks run as normal, the transfer passes, and her balance falls to GBP 347.01. The fee is recorded in its own account.
  3. Day 10, second transfer. She sends GBP 300 plus the same fee. Her balance falls to GBP 44.02.
  4. Day 12, a refused transfer. She tries to send GBP 100. The total to pay would take her balance below zero, so the app refuses and offers to load more. Nothing is sent on credit.
  5. Day 12, a mismatched load. She declares a top-up of GBP 200 but, in her banking app, types GBP 20.00. The deposit does not match the declaration, so it is held for review rather than credited. An operations analyst contacts her, she confirms the error, and the team follows its written procedure for mismatched deposits. Every step is recorded.

When finance samples her account at month-end, her statement agrees with the ledger entry for entry: one load, two transfers, two fees, and a held deposit that never reached her balance.

What the scenario shows: the controls that make wallets safe are mostly refusals. No funding without identity, no credit without a matching deposit, no transfer that takes a balance below zero.

09 · ROLLOUT

Rollout Checklist: Launching Wallets in Stages

Release gradually, so your team sees how loading, matching and support behave before volume arrives.

Before build

  • Written confirmation of whether your licence permits stored value in each market where you plan to offer it.
  • A safeguarding arrangement agreed with your bank and advisers, and a reconciliation schedule with a named owner.
  • Customer terms covering withdrawals, dormant balances and what happens if the business stops trading, published per country and language.
  • A procedure for returning stored value when a customer closes their account or a market is switched off.
  • A decision on loading limits and on how wallet-funded transfers count towards existing limits.

Before launch

  • Test on staging: exact and mismatched deposits, refused transfers, refunds and reversed entries.
  • A written procedure for held deposits, including who reviews them, how fast and what the customer is told.
  • Support scripts for "my balance hasn't updated" and "I sent the wrong amount".
  • Confirm that statements reconcile to the ledger for a sample of test accounts.

First weeks

  • Release to a limited group, such as established, verified repeat senders, before opening to everyone.
  • Review held deposits, refused transfers and loading patterns weekly.
  • Run the safeguarding reconciliation from day one.
10 · REMITSO

Doing it with RemitSo

RemitSo handles the mechanics below. Your team still owns licensing, safeguarding, policies and review of anything held.

  • Wallets in your own app, where your licence allows. Customers hold a balance, see it update live, load it by bank transfer and pay from it, which makes repeat transfers faster. See the customer app features.
  • Verified identity before funding. No one loads a balance until their ID is checked, which keeps unidentified money off your books.
  • Wallet countries as dated decisions. Switch wallets on or off per country with a recorded history; existing wallets are never touched, so a market can be paused without disturbing customers who already hold balances.
  • Versioned wallet terms. Terms are kept per country and language, and a published version is never edited, so you can show exactly what each customer accepted.
  • Wallet service in the admin panel. Your team can view a customer's wallet and return stored value from the console.
  • Balances from the books. A double-entry engine records every movement; balances cannot go below zero and entries are reversed, never edited, so finance and the customer see the same figure. See the admin features.
  • Deposits matched to the cent. Anything unclear is held, so a mistyped amount never becomes a wrong balance.
  • Chargebacks, recalls and double payments flagged. Alerts such as "Bank took money back" and "Duplicate payment captured" mean reversed or doubled loads are seen straight away, not at month-end.
  • Limits, screening and risk checks on every transfer. A wallet never bypasses your controls.
  • Staging first. Releases are tested on your staging environment before they reach customers. You can follow wallet changes in the release notes, or book a demo to see the flow end to end.
Do we need a separate licence to offer customer wallets?

It depends on your jurisdiction and current permission. In some places stored value needs an additional authorisation. Confirm with your regulator or advisers for each market before launch.

Why should a wallet balance never go below zero?

A negative balance means you have sent money on credit, and it complicates reconciliation against safeguarded funds. Refusing the transfer and offering a top-up is safer.

What should happen when a deposit does not match the declared load?

Hold it for a person to review. Crediting the nearest match risks the wrong amount reaching the wrong balance.

Do transfers paid from a wallet still need screening?

Yes. Every transfer should go through the same sanctions screening, limits and risk checks, whatever the source of funds. Loading patterns are worth watching on top of that.

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