Bill payments
Bill payments platform. Paid, fulfilled, and settled.
Flominzo Bills connects bill payments to biller validation, receipts, and settlement, so aggregators and fintechs can prove each bill was paid and fulfilled.
Last updated:
Book a Bills 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.
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.
Illustrative. Corridors, payout methods, rates and chat channels (WhatsApp included) are agreed for your deployment.
Agent PayonlineWhatsAppSend 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
Flominzo checkoutPayment amount£201.50- 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 PayoutsPayoutsonlineWhatsApp- 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.
BillsonlineWhatsAppAlso 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 BusinessBusinessonlineWhatsAppPay 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 worksRecononlineWhatsApp- 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 Bills is
Flominzo Bills is a bill payments product for bill aggregators, fintechs, wallets, and service platforms. It connects a customer’s bill-payment instruction to the biller’s validation, the payment, the receipt or token, and the biller’s final settlement, using the same intent, execution, and reconciliation model as the rest of Flominzo.
In bill payments, a successful charge is only half of the outcome. The customer also needs the service: a receipt, a prepaid token, or a credited account. Bills tracks payment and fulfilment separately, so a payment response never hides a missing service outcome.
How a bill payment moves through Bills
- Intent: The service, customer account, amount, and bill reference become one structured payment intent.
- Biller validation: The account and amount are checked where the connected biller or aggregator supports validation.
- Collection: The customer’s payment is collected and recorded as its own leg.
- Routing: The payment is routed to the biller or aggregator agreed for the service.
- Confirmation: The receipt, token, or confirmation is captured as evidence, linked to the payment.
- Settlement and closure: The biller’s settlement is reconciled with your records, and the payment closes when payment, fulfilment, and settlement agree.
Every Flominzo product runs through the same lifecycle: intent, plan and execution, rail adapters, events and ledger, reconciliation, and financial closure. Explore the architecture.
Services Bills can connect
Bills works with the services that a connected biller or aggregator supports, for example:
- Electricity, water, and internet.
- Mobile airtime and data.
- TV subscriptions.
- School fees and government payments.
- Insurance premiums and loan repayments.
- Transport and merchant services.
The billers, aggregators, and services available are agreed for your deployment.
Payment and fulfilment are tracked separately
| State | What it answers |
|---|---|
| Payment | Did the customer’s money move? |
| Fulfilment | Did the biller deliver the service: a receipt, a token, or a credited account? |
| Settlement | Did the biller or aggregator settle as expected? |
Keeping them apart makes the common bill-payment breaks visible: a customer who paid but has no token, a receipt with no settlement line, or a reversal after the receipt was issued. Each becomes an exception with its evidence attached.
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 bills, “matched” means the payment, the biller’s confirmation, and the settlement agree. A paid bill with a missing receipt stays open as an exception until the biller confirms it or a person records a decision, such as a refund.
See how Flominzo Recon reconciles every paymentWho Bills is for
- Bill aggregators connecting many billers and services.
- Fintechs and wallets offering bill payments to their customers.
- Remittance companies letting senders pay a family member’s bills directly.
- Service platforms that need proof of fulfilment as well as payment.
Start with one biller
Connect one biller and one service type first. Test invalid accounts, pending fulfilment, delayed receipts, reversals, and settlement mismatches, and agree who owns each exception, before adding more billers or services.
If you already run bill payments, Recon can reconcile your existing payments, confirmations, and biller settlements while you decide what to move.
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
Does Bills connect directly to billers?
Bills connects through rail adapters to the billers and aggregators you use or choose. Which billers, services, and markets are live is agreed for your deployment.
What if the customer pays but the token never arrives?
The payment stays open with a fulfilment exception. Your team sees the payment evidence, the missing receipt, and the biller’s response in one place, and the decision to re-query or refund is recorded.
How are biller settlements reconciled?
Biller and aggregator settlement reports are matched with the payments and confirmations they cover. Missing lines, amount differences, and fees outside tolerance become exceptions with owners.
Can customers pay bills in a chat?
Yes, through Flominzo AgentPay. “Pay my electricity bill” resolves into the same structured bill-payment intent, with the same validation and limits.
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