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 chapter of Kwame’s day, run through a chat. The same limits, approvals and evidence govern it as every other payment.
Send, in four steps
SendonlineWhatsApp- 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.
Corridors, payout methods, rates and chat channels (WhatsApp included) are agreed for your deployment.
Early-bird offer
Flominzo 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.
On this page 10 sections
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.
A transfer, step by step
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 |
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 and payout platforms 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