Flominzo

Payment products

Six payment products. One financial foundation.

Payment products for remittance, payouts, business payments, bills, reconciliation, and agent-initiated payments. Start with the one your team needs today.

Last updated:

Consumer payments

Flominzo Send

Consumer & remittance payments

Bring the sender’s instruction, the recipient’s payout, and the resulting financial evidence into one payment journey. Flominzo Send is the consumer and remittance surface of the shared platform.

  • Capture the beneficiary, amount, currency, and intended payout method in one payment intent.
  • Follow collection, FX where required, payout, and settlement as connected stages.
  • Give operations a traceable record when delivery is delayed or an outcome needs investigation.
Explore remittance solutions
SendonlineWhatsApp
1Who gets it, and how?
  • Mobile moneyAma Mensah · MTN •••• 4417Minutes
  • Bank accountAma Mensah · GCB •••• 0092Same day
  • Cash pickupAma Mensah · KumasiToday
2Amount and rate
You send
£200.00
Rate, locked 10 min
1 GBP = 15.60 GHS
Fee
£1.50
Mum receives
GH₵ 3,120.00
3PayPayment amount£201.50
  • Pay by bankBarclays
  • CardVisa •••• 4242
Pay £201.50
4Track
  • Paid inDone
  • ConvertedDone
  • Mobile moneyPaid
Delivered to Mum
Last month · Money home took four steps. Illustrative. Corridors, payout methods, rates and chat channels (WhatsApp included) are agreed for your deployment.

Payout infrastructure

Flominzo Payouts

Payout routing & execution

Connect payout providers through a common execution model. Flominzo Payouts separates the instruction to move money from the partner-specific API that carries it out.

  • Route execution through the enabled providers and policies agreed for your environment.
  • Track each attempt without losing the original payment instruction.
  • Investigate an unknown result before deciding whether a retry or another route is safe.
Explore payout platform solutions
PayoutsonlineWhatsApp
Payout · TX-20418
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
Paid once
14:02 · Behind the chat, the payout is routed and checked. Illustrative. Routing follows the rules you configure; the assistant explains decisions and never moves money. Chat channels are agreed for your deployment.

Business payments

Flominzo Business

Supplier, payroll & bulk payments

Organise business disbursements around the people, invoices, and batches your team already works with. Individual payments retain their own execution and financial history.

  • Connect supplier payments, payroll, and bulk disbursements to the common financial core.
  • Apply the approval and access boundaries agreed for your business workflow.
  • Distinguish completed, outstanding, and exception items instead of treating a submitted batch as settled.
Explore business operations solutions
BusinessonlineWhatsApp

Pay all approved invoices due tomorrow, but nothing above £10,000 without asking me.

Due tomorrow · approved
  • Sharma TextilesINV-2231 · ₹85,000.00Approved by Sarah
  • Accra WeaversINV-118 · GH₵ 48,000.00Approved
  • Kumasi LogisticsINV-77 · £12,400.00Over £10,000
Rates locked for 30 minutes
₹85,000 at 118.00
£720.34
GH₵ 48,000 at 15.60
£3,076.92
Total
£3,797.26
Approve payment run

Approve. Hold Kumasi until I’ve checked the delivery.

  • Sharma TextilesPaid
  • Accra WeaversPaid
  • Kumasi LogisticsHeld
2 paid and matched
16:30 · Back at work: the company’s invoices. Illustrative. Mandates, approval rules, payout partners and chat channels are agreed for your business.

Bill payments

Flominzo Bills

Bill & service payments

Connect bill-payment instructions to the biller’s response, customer receipt, and settlement evidence. Flominzo Bills uses the same intent, execution, and reconciliation model as the other products.

  • Identify the service, customer account, amount, and reference before execution.
  • Use the validation and receipt capabilities available through the connected biller.
  • Track fulfilment and settlement separately so a payment response does not hide a missing service outcome.
Explore bill aggregator solutions
BillsonlineWhatsApp

Also put GH₵ 150 on Mum’s electricity meter.

Biller check
Service
Electricity · prepaid
Meter
0412 •••• 7719
Account name
A. Mensah
You pay
£9.62 (GH₵ 150.00)
Confirm and pay

Confirm

Paid. The token is 4829 1177 0356 2210 5841, and I’ve sent it to Mum.

  • Biller responsePaid
  • TokenDelivered
  • Biller settlementMatched
Reconciled
14:10 · A bill for Mum, paid and proven. Illustrative. Validation and receipts depend on each connected biller; chat channels are agreed for your deployment.

Agentic operations

Flominzo Recon

Reconciliation & financial closure

Connect the records your systems produce to independent partner and bank evidence. Flominzo Recon gives teams a path from an unexplained difference to an evidence-backed financial decision.

  • Start with read-only transaction sources while existing systems keep running.
  • Compare payment records, execution events, settlement files, and bank statements.
  • Investigate exceptions, retain the reason for each decision, and reopen closure when later evidence requires it.
Explore finance & treasury solutions
RecononlineWhatsApp
Exception · API paid, file missing
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.

Recommended resolution
Action
Match to the 24 September file
Evidence
2 records attached
Approve

Approve.

Recorded your decision. TX-20418 is reconciled, with the evidence and your approval in its history.

Next morning · The books close, with proof. 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

Flominzo AgentPay

Conversational payment initiation

Turn a natural-language request into a structured payment instruction. Flominzo AgentPay provides an interaction layer over the same controlled execution path used by the rest of the platform.

  • Resolve the requested beneficiary, amount, currency, and purpose into an explicit intent.
  • Check the applicable mandate, limits, permissions, and approval requirements.
  • Keep payment execution inside deterministic controls; an agent’s recommendation is not financial proof.
Explore controlled business workflows
Agent PayonlineWhatsApp

Send Mum £200 for school fees.

Mum has two saved accounts. Where should it go?
  • Mobile moneyMTN •••• 4417Minutes
  • Bank accountGCB •••• 0092Same day

Mobile money, like last time.

Payment intent
To
Ama Mensah · MTN, Ghana
Rate, locked 10 min
1 GBP = 15.60 GHS
Fee
£1.50
Mum receives
GH₵ 3,120.00
Flominzo checkoutPayment amount£201.50
  • Pay by bankBarclays
  • CardVisa •••• 4242
Confirm and pay
  • Paid inDone
  • ConvertedDone
  • Mobile moneyPaid
Sent within your daily limit

Did it arrive?

Yes. Mum was paid at 14:02, and the partner’s records confirm it.

13:58 · Now Kwame asks in a chat. Illustrative conversation. Chat channels, WhatsApp included, are agreed for your deployment.

Inside the operations console

One console for every product.

Teams work exceptions from a queue, see each payment’s operational and financial states side by side, and close a business day only when nothing is left unexplained.

Flominzo operations console, exception queue. Eight open exceptions with their type, owner, raised and due-by times, overdue flag, payment, status, and evidence count, including SETTLEMENT_MISMATCH, UNKNOWN_UNRESOLVED, and FILE_MISSING.
Exception queue: every break has a type, an owner, and a due-by time. Console view rendered from the product’s own interface with synthetic data.
Flominzo operations console, payment screen. The operational state is PAID while the financial side shows MISMATCHED and OPEN, with legs, attempts, settlement, ledger postings, an evidence timeline graded CLAIM, SETTLEMENT and CASH, the open exception, and the Recon Agent's recommendation marked as not a decision.
Payment screen: operational and financial states side by side, never one status. Console view rendered from the product’s own interface with synthetic data.
Flominzo operations console, business-day draft for 23 September. Three blockers prevent closing the day: a missing settlement report, an open settlement mismatch, and an unexplained ledger position, followed by expected files, open payments, settlements, and balances.
Business-day draft: the day cannot close while a blocker remains. Console view rendered from the product’s own interface with synthetic data.

Integration

Your systems stay.
Flominzo connects them.

No rip and replace. Our team connects Flominzo to what you run today, however legacy or fragmented, and proves one flow with you before anything else changes.

  1. Integrate once. Every provider sits behind one Rail Adapter contract, so a new provider changes one adapter, never your core. Rail Adapter Contract
  2. Start alongside what runs today. Reconciliation reads your existing sources and evidence while current workflows keep running.
  3. Go live one flow at a time. One payment flow or one reconciliation challenge, mapped and validated with you. Explore the REST API