Remittance software
Remittance software from quote to payout. Every transfer reconciled.
Remittance software for money transfer operators: FX quotes, collection, payout routing, partner settlement, and every transfer reconciled to closure.
Last updated:
Book a demoWhat remittance software does
Remittance software runs the lifecycle of an international money transfer: the sender’s quote and payment, the currency conversion, the payout to the recipient’s bank account or wallet, and the settlement with each partner that carried it. Flominzo connects those stages on one payment core, so each transfer keeps one reference from the first quote to financial closure.
Most operators already have parts of this: an app, a core transaction database, several payout partners, and a finance team reconciling files. Flominzo is built to connect those parts rather than replace them, and to answer the question every operator eventually asks: did this transfer really arrive, once, for the right amount, and has the partner settled it?
Our answer 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.
The remittance lifecycle, stage by stage
| Stage | What must happen | What Flominzo records |
|---|---|---|
| Quote and FX lock | The sender sees the rate, the fee, and what the recipient receives, and the rate is held for a set time. | The booked quote, later compared with the rate the partner applied. A difference beyond tolerance raises FEE_FX_MISMATCH. |
| Collection | Funds are collected from the sender by card, bank transfer, or wallet. | The collection as its own leg, with its own evidence. |
| Compliance checks | Screening, KYC, and AML checks run in your compliance programme or with your providers. | The checks and approvals required before execution, as agreed for your deployment. Flominzo does not replace your compliance programme. |
| Payout routing | The payout goes to an eligible partner for the corridor and method. | Each attempt, its provider reference, and its classified result. |
| Partner settlement | Prefunded or postpaid partners settle on their own schedule and cut-offs. | Settlement lines matched to payouts, and partner positions matched to their statements. |
| Reconciliation and closure | Every record of the transfer agrees, or the difference is explained. | A financially closed transfer, or an open exception with an owner. |
Where remittance operations lose money
Remittance margins are thin, so small, repeated differences matter. They rarely come from one dramatic failure. They come from the same few situations happening quietly across partners and corridors:
- Duplicate payouts after a partner times out and the transfer is resent before anyone checks whether the first attempt arrived.
- FX and fee drift when the rate or fee a partner applies differs slightly from the quote the sender accepted.
- Unexplained partner balances when a prefunded float no longer matches the partner’s statement and no single transfer explains why.
- Reversals after success when a payout reported as paid is returned days later, after the sender has been told it arrived.
- Missing files when a settlement report does not arrive and the day is closed as if nothing were missing.
Each of these becomes a named exception in Flominzo, with an owner and the evidence attached, instead of a difference found at month-end.
Flominzo Send: the customer journey
Flominzo Send is the consumer and remittance surface of the platform. Transfers can start from a mobile app, a web app, an API, or an embedded interface, and resolve into one canonical payment intent: who is paying, who receives, the amount and currencies, and the payout method.
Payout methods can include bank transfer, mobile money, wallets, and cash pickup, depending on the partners connected for your corridors. Beneficiary management, quotes, and transaction tracking sit on the same record your operations team investigates.
Illustrative example: a sender in London sends GBP 200.00 to a mobile-money wallet in Ghana at 1 GBP = 15.60 GHS, so the recipient receives GHS 3,120.00. The names, rate, and fee in examples on this site are not a customer’s results.
Explore Flominzo SendPartner prefunding and settlement
Payout partners settle in different ways. Each partner’s profile declares its settlement model - prefunded or postpaid - its frequency, cut-offs, currency, and accounts, and which files or statements it delivers and when.
That declaration lets Flominzo reconcile at three levels: each payout against its evidence, each settlement against the payouts it covers and the bank movement, and each partner balance against the partner’s statement. When a prefunded balance drifts and no single payout explains why, it raises POSITION_UNEXPLAINED instead of waiting for month-end.
Agentic initiation with AgentPay
Senders increasingly ask for a transfer in a chat rather than a form. Flominzo AgentPay turns a request such as “send £200 to Mum’s MTN wallet” into an explicit payment intent, then checks the mandate, limits, permissions, and approvals that apply.
Agents interpret and prepare. They never move money on their own: execution stays inside the deterministic payment core, and the same reconciliation applies to every transfer, however it started.
Explore Flominzo AgentPayPlan by sending market
Rails, regulators, and statement formats differ by market. Each guide sets out what to plan for when sending from, or paying out in, that market.
What to check when choosing remittance software
| Question | Why it matters |
|---|---|
| Does one reference follow a transfer from quote to closure? | Without it, support and finance investigate the same transfer in different systems. |
| Is the booked FX rate compared with the rate the partner applied? | Small rate or fee differences add up across partners and corridors. |
| What happens when a payout partner times out? | Resending an uncertain payout is the most common cause of duplicate payments. |
| Can you add or switch a payout partner without rebuilding? | Partner changes, API retirements, and new corridors are routine in remittance. |
| Are partner balances reconciled against their statements? | Prefunded floats can drift for weeks before anyone notices. |
| Does it work with your existing core and compliance systems? | A platform that requires replacing everything takes the longest to deliver value. |
Questions
Does Flominzo perform KYC or sanctions screening?
No. Screening, KYC, and AML checks stay with your compliance programme or your providers. Flominzo records the checks and approvals required before execution, as agreed for your deployment.
Do we have to replace our current remittance platform?
No. Many operators start with reconciliation, reading existing transaction records and partner files while the current platform keeps running, then add execution where it helps.
Which corridors are supported?
Flominzo connects through rail adapters to the providers you use; rails, markets, and activation are agreed for your deployment.
What does 100% reconciliation mean for a transfer?
It means 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.
How is it priced?
Pricing depends on your corridors, partners, and volumes. See how we charge.
Let’s make it specific to you.
Bring your systems, payment flows, and questions. We’ll help define the next step.
Talk to the team