Mobile money payouts, reconciled wallet by wallet.

What a mobile money payout is

A mobile money payout sends funds to a recipient’s mobile wallet, identified by a phone number on a service run by a mobile network operator, such as M-Pesa, MTN MoMo, or Airtel Money. The payout is quick to request but harder to prove: operators and aggregators confirm it through callbacks and daily files that can arrive late, disagree, or be reversed.

Flominzo treats each wallet payout as a payment that is open until the evidence agrees. That is agentic payments with 100% reconciliation: every payment ends either matched against independent evidence - the provider’s records, the settlement file and the bank statement - or as an open exception with an owner and a reason. None is silently assumed paid.

Wallet names on this page describe the market. They are not a list of Flominzo integrations; providers are connected through rail adapters to the providers you use, and rails, markets, and activation are agreed for your deployment.

Where mobile money payouts are used

Mobile wallets are a primary way to receive money in much of East and West Africa, and are widely used in parts of South and South-East Asia. Typical sending markets include the United Kingdom, the United States, the UAE and the Gulf, Canada, and Australia.

Before the payout: checks that prevent problems

The cheapest wallet problem is the one that never happens. Before a mobile money payout is sent, Flominzo resolves it into an explicit instruction - the wallet number, network, recipient name, amount, and currency - and applies the checks your deployment requires.

• Confirm the number belongs to the expected network and, where the provider supports a lookup, that the registered name matches the recipient.
• Check the amount against the wallet and provider limits declared in the provider’s profile.
• Record the quote the sender accepted, so the rate and fee the partner applies can be compared with it later.
• Attach an idempotency key, so a repeat of the same instruction can never become a second payout.

What goes wrong, and how it is handled

An illustrative payout, end to end

1. A sender pays GBP 200.00. At 1 GBP = 15.60 GHS, the recipient should receive GHS 3,120.00 in an MTN MoMo wallet in Ghana.
2. The name check returns the expected name, and the payout is sent to Partner B with an idempotency key.
3. Partner B times out. The attempt is recorded as unknown, and no second payout is sent.
4. A status lookup returns paid. The payment is paid, but still open.
5. The next morning, Partner B’s settlement file lists the payout, and the bank movement for the settlement agrees.
6. Every record agrees, so the payment is financially closed.

Illustrative. The names, partner, and rate are examples, not a customer’s results.

After the payout: telling the sender the truth

Senders want to know that the money arrived. Support teams need to answer without guessing. Because every record of the payout sits on one payment, Flominzo can separate what is known from what is still being proven: sent, paid according to the provider, or settled and financially closed.

When something is uncertain - a timeout, a late callback, a reversal - the payment shows why it is open and who owns the next step. Support and finance read the same history, so the answer a sender receives matches what the evidence says.

Reconciling mobile money payouts to closure

Wallet payouts need reconciling at three levels. Each payout is checked against the provider’s claims and settlement lines. Each settlement is checked against the payouts it covers and the bank movement that funds it. Each prefunded float is checked against the operator’s or aggregator’s statement.

Evidence is ranked: a bank movement outranks a settlement file, a settlement file outranks a callback, and a callback outranks your own records. Operator and aggregator files are read through configured CSV layouts, and bank statements through ISO 20022 camt.053 and camt.052 or SWIFT MT940.

Questions

Related reading