Business payments
Bulk, supplier, and payroll payments. Every item accounted for.
Flominzo Business runs bulk, supplier, and payroll payments for companies and marketplaces: one instruction, thousands of payments, each one reconciled.
Last updated:
Book a Business 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 Business is
Flominzo Business is a bulk payments product for supplier payments, payroll, and mass disbursements. It is built for companies, marketplaces, payroll operators, gig platforms, and finance teams that turn one business instruction into hundreds or thousands of individual payments.
A submitted batch is not a paid batch. Business keeps every item in a batch as its own payment, with its own execution, evidence, and financial state, so finance can see exactly what was paid, what is still processing, and what needs attention.
From one instruction to thousands of payments
- Instruction: A batch arrives from a payment file, an ERP export, an API call, or an AgentPay request, and follows the approval workflow agreed for your business.
- Batch and plans: Each item is validated for beneficiary, amount, currency, and reference, and receives its own payment plan.
- Routing and execution: Items are routed through Flominzo Payouts to eligible providers. Each attempt carries an idempotency key and a recorded result.
- Events and ledger: Every item’s events are appended to its history, and the ledger records the financial effect.
- Reconciliation: Each item is compared with provider, settlement, and bank evidence.
- Batch closure: The batch closes when every item is financially closed or explained.
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 batch report
A company pays 4,800 field agents their monthly payments. Instead of reporting “4,800 submitted”, Business reports the state of every item.
| State | Items |
|---|---|
| Instructed | 4,800 |
| Paid | 4,797 |
| Processing | 2 |
| Exception | 1 |
| Financially closed | 4,710 |
| Settlement pending | 90 |
Illustrative example with synthetic numbers.
What you can run
- Supplier payments against approved invoices.
- Payroll and contractor payments.
- Marketplace and seller payouts, connected to the orders, commissions, and adjustments behind them.
- Bulk and mass disbursements.
- Cross-border B2B payments, with FX captured for each item.
Approvals and controls
- Approval boundaries: who can create, approve, and release a batch is agreed for your workflow.
- Mandates and limits: for example, “nothing above £10,000 without approval” (illustrative).
- Beneficiary checks: name lookup and validation where the provider supports them.
- Idempotency on every item: a retried submission does not create a second logical payment.
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 batch, every one of the thousands of items is matched or raised. A payment returned days later reopens that item, with its earlier evidence preserved, instead of silently changing a batch total.
See how Flominzo Recon reconciles every paymentWho Business is for
- Finance teams running supplier and invoice payments.
- Payroll operators and companies paying staff, agents, or contractors.
- Marketplaces and gig platforms paying sellers and workers.
- Enterprises consolidating payments that span spreadsheets, ERP records, and several banking interfaces.
Start with one workflow
Begin with one supplier or payroll workflow. Agree the source records, approvals, beneficiary checks, and the evidence required to close each payment, then run it alongside your current process before adding more payment types.
Existing systems keep their jobs: your ERP stays the source of approved invoices, and your bank connections can remain in place while Business and Recon build the connected view.
See the integration approachMarkets
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
Can we upload a payment file from our ERP?
Batches can come from a file, an ERP export, an API call, or an AgentPay request. The formats and mapping for your source are agreed during integration.
What happens when one payment in a batch fails?
Only that item becomes an exception, with its reason and owner. The rest of the batch continues, and the batch report shows the item separately instead of hiding it in a total.
Does Business work with our existing bank?
Business executes through the providers and bank connections agreed for your deployment, and it can reconcile payments made through your existing banking interfaces while you move over.
Can we pay contractors in other countries?
Yes, where the providers agreed for your deployment cover the corridor. Each cross-border item captures its quote, rate, and fee, and the FX the provider applied is reconciled against it.
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