Bulk payments API and platform. Every item accounted for.

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

1. 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.
2. Batch and plans: Each item is validated for beneficiary, amount, currency, and reference, and receives its own payment plan.
3. Routing and execution: Items are routed through Flominzo Payouts to eligible providers. Each attempt carries an idempotency key and a recorded result.
4. Events and ledger: Every item’s events are appended to its history, and the ledger records the financial effect.
5. Reconciliation: Each item is compared with provider, settlement, and bank evidence.
6. 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.

A batch report, item by item

A company pays 4,800 field agents their monthly payments. Instead of reporting “4,800 submitted”, Business reports the state of every item.

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: such as “nothing above £10,000 without approval”.
• 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.

Who 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.
• SMEs and 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.

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.

Related products

Questions

Related guides