Agentic payments
Agentic payments inside your limits. Agents ask. Controls decide.
Flominzo AgentPay lets people and AI agents start payments in plain language, within your limits. Early-bird: $3,999 setup plus $999 a month.
Last updated:
Explore AgentPay pricingAgentic 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 AgentPay is
Flominzo AgentPay is an agentic payments product. It lets people, businesses, and AI agents initiate payments in natural language, and turns each request into a structured payment instruction that the deterministic payment core executes under mandates, limits, and approvals. It is built for fintechs, wallets, remittance companies, and businesses that want conversational or agent-initiated payments without giving an AI model control of money.
The principle underneath is simple: AI understands and orchestrates intent; deterministic systems control money.
AgentPay early-bird pricing
$3,999 setup + $999 a month, for the first 20 customers. The setup covers 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.
From a sentence to a controlled payment
- Request: A person, a business copilot, or an external AI agent asks for a payment in natural language.
- Intent understanding: The beneficiary, amount, currency, timing, and purpose are resolved. Anything ambiguous is asked back, not guessed.
- Structured payment intent: The request becomes the same canonical intent every other Flominzo product uses.
- Validation: Beneficiary, limits, balance, and permissions are checked.
- Confirmation or mandate: The person confirms, or a pre-approved mandate covers the payment. Anything outside the mandate is held for a person.
- Deterministic execution: The payment runs through Send, Payouts, Business, or Bills, then through reconciliation to financial closure.
Every Flominzo product runs through the same lifecycle: intent, plan and execution, rail adapters, events and ledger, reconciliation, and financial closure. Explore the architecture.
Illustrative requests
| Request | What AgentPay resolves |
|---|---|
| “Send £100 to Mum in Ghana.” | A Send intent to a saved beneficiary, with a quote to confirm. |
| “Pay my electricity bill.” | A Bills intent, validated with the biller before payment. |
| “Pay Sharma Textiles’ ₹85,000 invoice after Sarah approves it.” | A Business payment held for a named approver. |
| “Pay all approved invoices due tomorrow, but nothing above £10,000 without asking me.” | A mandate: a scheduled batch with a per-payment limit. |
Illustrative examples. Names and amounts are fictional.
Mandates, limits, and approvals
A mandate is the standing authority an agent acts within: who or what it may pay, how much, how often, and when a person must confirm. AgentPay checks the applicable mandate before any instruction reaches execution.
- Limits per payment, per day, and per beneficiary.
- Approval requirements by amount, beneficiary, or payment type.
- Idempotency, so a repeated request does not create a second payment.
- State machines, ledger controls, routing policies, reconciliation controls, and financial closure rules that no agent can bypass.
What agents can and cannot do
Agents read, interpret, draft, and explain. They can request a deterministic action through the same controlled commands a person would use. Agents never, on their own:
- move money or change a payment, posting, or ledger entry;
- resolve an unknown outcome by assumption or override idempotency;
- change limits, routing policy, or reconciliation rules;
- close an exception or accept a settlement.
Every tool call an agent makes is recorded as an event with the agent as the actor.
Read the security controlsChannels
AgentPay is channel-independent. A messaging app such as WhatsApp, a mobile or web app, voice, an AI assistant, a business copilot, or an external AI agent all resolve to the same structured intent. The channels enabled for you are agreed for your deployment.
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.
An agent’s recommendation is not financial proof. Every payment an agent starts goes through the same reconciliation as any other, so you can show exactly what an agent asked for, what was approved, what executed, and what the provider and bank recorded.
See how Flominzo Recon reconciles every paymentWho AgentPay is for
- Fintechs and wallets adding conversational payments.
- Remittance companies offering transfers started in a chat.
- Businesses using copilots to prepare and release invoice runs.
- Platforms that let external AI agents pay, under mandates they control.
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
Can an AI agent move money on its own?
No. An agent produces a structured intent. Execution happens only in the deterministic payment core, after validation and a confirmation or a mandate check.
Which AI assistants or agents does AgentPay work with?
AgentPay is the controlled boundary between an agent and the payment core. The interfaces and agents connected are agreed for your deployment; whichever model interprets the request, execution passes through the same checks.
What if the agent misunderstands the request?
Nothing executes on an ambiguous intent. The structured intent is validated and shown for confirmation, or checked against a mandate, first. A request outside the mandate is held for a person.
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