Bill payment API and platform. Paid, fulfilled, and settled.

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

1. Intent: The service, customer account, amount, and bill reference become one structured payment intent.
2. Biller validation: The account and amount are checked where the connected biller or aggregator supports validation.
3. Collection: The customer’s payment is collected and recorded as its own leg.
4. Routing: The payment is routed to the biller or aggregator agreed for the service.
5. Confirmation: The receipt, token, or confirmation is captured as evidence, linked to the payment.
6. 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

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.

Who Bills is for

• Bill and service 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.

Related products

Questions

Related guides