Remittance payments
Cross-border money transfer. From sender to proven payout.
Flominzo Send is a cross-border money transfer product for remittance companies and fintechs: quote, collect, pay out, and reconcile every transfer.
Last updated:
Book a Send demoAgentic payments
Payments, built for agents.
One day with Kwame: money home to his mum, the old way and then in one sentence, a bill for her, his company’s invoices, and the close. The same limits, approvals and evidence govern every step.
- You send
- £200.00
- Rate, locked 10 min
- 1 GBP = 15.60 GHS
- Fee
- £1.50
- Mum receives
- GH₵ 3,120.00
- Pay by bankBarclays
- CardVisa •••• 4242
- Paid inDone
- ConvertedDone
- Mobile moneyPaid
Kwame picks who gets the money and how it arrives, sees the locked rate and the full price, pays, and follows the payment through collection, FX, payout and settlement. Every step lands in one payment record.
Illustrative. Corridors, payout methods, rates and chat channels (WhatsApp included) are agreed for your deployment.
Send Mum £200 for school fees.
Mobile money, like last time.
- To
- Ama Mensah · MTN, Ghana
- Rate, locked 10 min
- 1 GBP = 15.60 GHS
- Fee
- £1.50
- Mum receives
- GH₵ 3,120.00
- Pay by bankBarclays
- CardVisa •••• 4242
- Paid inDone
- ConvertedDone
- Mobile moneyPaid
Did it arrive?
Yes. Mum was paid at 14:02, and the partner’s records confirm it.
The same payment, in one sentence. AgentPay works out who, how and how much, asks only what it can’t know, locks the rate, and takes payment in the chat. Underneath, the same core, limits and approvals run it, and “did it arrive?” is answered from evidence.
Illustrative conversation. Chat channels, WhatsApp included, are agreed for your deployment.
14:02 · Behind the chat, the payout is routed and checked.
Payout infrastructurePayouts, routed live
Explore Flominzo Payouts- To
- Ama Mensah · MTN, Ghana
- Amount
- GH₵ 3,120.00
- Route
- Partner B
Why Partner B? We usually use Partner A for Ghana.
Partner A’s MTN success rate fell to 71% in the last hour, below your 95% policy, so routing chose Partner B.
Partner B then timed out, so the outcome was unknown. Nothing was retried: I asked Partner B for the status instead.
- Status checkPaid 14:02
- Duplicate payoutNone
- Partner fileAwaited
Kwame’s instruction reaches the payout network once. Flominzo routes it through the partners and policies agreed for the business, keeps every attempt against the original instruction, and treats an unknown result as something to check, not something to retry blindly.
Illustrative. Routing follows the rules you configure; the assistant explains decisions and never moves money. Chat channels are agreed for your deployment.
Also put GH₵ 150 on Mum’s electricity meter.
- Service
- Electricity · prepaid
- Meter
- 0412 •••• 7719
- Account name
- A. Mensah
- You pay
- £9.62 (GH₵ 150.00)
Confirm
Paid. The token is 4829 1177 0356 2210 5841, and I’ve sent it to Mum.
- Biller responsePaid
- TokenDelivered
- Biller settlementMatched
Flominzo checks the meter with the biller before any money moves, pays through the connected biller or aggregator, and tracks the service and the settlement separately, so a paid response never hides a missing token.
Illustrative. Validation and receipts depend on each connected biller; chat channels are agreed for your deployment.
16:30 · Back at work: the company’s invoices.
Business paymentsInvoices, on a mandate
Explore Flominzo BusinessPay all approved invoices due tomorrow, but nothing above £10,000 without asking me.
- Sharma TextilesINV-2231 · ₹85,000.00Approved by Sarah
- Accra WeaversINV-118 · GH₵ 48,000.00Approved
- Kumasi LogisticsINV-77 · £12,400.00Over £10,000
- ₹85,000 at 118.00
- £720.34
- GH₵ 48,000 at 15.60
- £3,076.92
- Total
- £3,797.26
Approve. Hold Kumasi until I’ve checked the delivery.
- Sharma TextilesPaid
- Accra WeaversPaid
- Kumasi LogisticsHeld
Kwame sets the rule once; the agent applies it. Approved invoices are paid to the right supplier, in their currency, at a locked rate, and anything outside the mandate waits for him. Each payment keeps its own execution and history.
Illustrative. Mandates, approval rules, payout partners and chat channels are agreed for your business.
Next morning · The books close, with proof.
Agentic operationsRecon Agent
See how reconciliation works- Payment
- TX-20418
- Provider API
- Paid 14:02
- Partner file, 23 Sep
- Not listed
The provider says PAID, but the 23 September partner file doesn’t list Mum’s payout.
That file closes at 14:00 and the payout landed at 14:02. It’s in the 24 September file: same reference, same amount.
- Action
- Match to the 24 September file
- Evidence
- 2 records attached
Approve.
Recorded your decision. TX-20418 is reconciled, with the evidence and your approval in its history.
An agent that works your exception queue. It correlates evidence across providers, partner files and bank statements, explains what it found in plain language, and recommends a resolution. You approve what happens next.
The Recon Agent never moves money and never changes a state. A person approves every resolution. Chat channels are agreed for your deployment.
Agentic payments
AgentPay
$3,999 setup + $999 a month
Early-bird for the first 20 customers: integration with your providers and bank or settlement files by the Flominzo team, every payment reconciled to closure, and the operations console. Month to month, no minimum term.
What Flominzo Send is
Flominzo Send is the remittance and cross-border money transfer product of the Flominzo platform. It is built for remittance companies, money transfer operators, and fintechs that move money for their customers, and it connects the sender’s instruction, the FX step, the recipient’s payout, and the resulting financial evidence into one payment journey.
Many transfer stacks track a transfer as one status on one row. Send keeps each stage - collection, FX, payout, and settlement - as its own record with its own evidence. Your customer sees a clear status, and your operations team sees exactly which stage is complete and which is still waiting for proof.
How a transfer moves through Send
- Intent: The sender’s request becomes one canonical payment intent: sender, beneficiary, amount, currencies, payout method, and purpose. A request from your app, website, API, or an AgentPay conversation resolves to the same structure.
- Quote and plan: The quote records the rate, fee, and validity window. The plan splits the transfer into execution legs: collection, FX where required, and payout.
- Execution through rail adapters: Each leg runs through the adapter for the provider that carries it. Every attempt is recorded with its provider reference and a result class.
- Events and ledger: Each step is appended to the event history, and the double-entry ledger records the financial effect in each currency.
- Reconciliation: Provider claims, webhooks, settlement files, and bank statements are compared with what Send instructed.
- Financial closure: The transfer closes only when the required evidence agrees. Late evidence reopens it with its history intact.
Every Flominzo product runs through the same lifecycle: intent, plan and execution, rail adapters, events and ledger, reconciliation, and financial closure. Explore the architecture.
An illustrative transfer
A sender in London sends money to a family member’s mobile-money wallet in Ghana.
| Step | Value |
|---|---|
| You send | GBP 200.00 |
| Rate, locked for the quote window | 1 GBP = 15.60 GHS |
| Fee | GBP 1.50 |
| Recipient receives | GHS 3,120.00 |
| Payout method | Mobile money |
| Closes when | The provider confirmation, the settlement line, and the bank movement agree |
Illustrative example. Rates, fees, corridors, and payout methods depend on the providers and markets agreed for your deployment.
What Send handles
- International remittance and domestic transfers from one payment model.
- Payout by bank transfer, mobile money, wallet, cash pickup, or other local rails that the connected providers support.
- Quotes, FX, and fees captured with the instruction, then checked against what the provider applied.
- Beneficiary management, with name lookup where the provider supports it.
- Transaction tracking through every stage, instead of one mutable status.
- Automatic payout routing through Flominzo Payouts.
- End-to-end reconciliation and financial closure through Flominzo Recon.
- Conversational initiation through Flominzo AgentPay, inside the same controls.
100% reconciliation built in
Every payment ends either matched against independent evidence (provider, settlement file, bank statement) or as an open exception with an owner and a reason - none is silently assumed paid.
For a remittance business, a transfer marked paid in your app but missing from the partner’s daily file becomes a visible exception when the file arrives, not a customer complaint weeks later. The rate and fee the provider applied are checked against the booked quote, and a reversal after payout reopens the transfer with its earlier evidence preserved.
See how Flominzo Recon reconciles every paymentWho Send is for
- Remittance companies and money transfer operators running one corridor or many.
- Fintechs and wallets adding international transfers to an existing app.
- Payment institutions that want a controlled transfer journey alongside their existing systems.
- Teams that already run transfers and want to prove the evidence model before moving execution.
Send works alongside what you already run. You can start with Flominzo Recon on your current transfers, then move one corridor onto Send once reconciliation is proven on your own records.
Markets
Rails, statement formats, and regulation differ in each market. Flominzo is connected through rail adapters to the providers you use; markets, rails, and activation are agreed for your deployment.
Questions
Which corridors and payout methods does Send support?
Send is connected through rail adapters to the providers you use. Corridors, currencies, payout methods, and activation are agreed for your deployment, starting with one corridor and one payout method that you can prove end to end.
Does Flominzo replace our current transfer platform?
No. Send can run alongside your existing platform. A reconciliation-first start reads your current transaction records and evidence, so you can prove the model before moving any execution.
What happens if a payout times out?
The attempt is recorded as an unknown outcome. Send resolves it by a status lookup or settlement evidence, never by sending the payout again, so a timeout does not become a duplicate payment.
Can our customers start a transfer in a chat?
Yes, through Flominzo AgentPay. A conversational request becomes the same structured payment intent, and the same limits, mandates, and approvals govern execution.
Related guides
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