Payment architecture
One connected payment path. From intent to financial closure.
The Flominzo payment architecture: one financial core for orchestration, a double-entry ledger, and reconciliation. Instructions, attempts, and evidence stay connected.
Last updated:
One shared financial core
Every product enters the same lifecycle.
Send, Payouts, Business, Bills, Recon and AgentPay are product surfaces over one foundation. Each brings a different entry point into the same controlled financial lifecycle.
The lifecycle
One payment, six connected records.
Follow TX-20418, Kwame’s £200 to his mum, through the core. The stages are connected records, not a promise that every payment completes at once: delays, exceptions and later adjustments stay visible.
Payment intent
Capture the instruction and its authority.
£200 to Ama Mensah · MTNPlan & execution
Resolve the steps and record each attempt.
Collect · FX · PayoutConnected rails
Execute through the enabled provider adapters.
Partner B · MTN MoMoEvents & ledger
Record what happened and its financial effect.
Every posting balancedReconciliation
Compare records with independent evidence.
3 of 3 sources matchedFinancial closure
Resolve differences and preserve the proof.
Reconciled, with evidence
One intent model
A payment starts with a canonical instruction: who is paying, who should receive value, the amount and currency, and the applicable authority. A mobile journey, API request, business batch or agent conversation must resolve into an explicit intent.
A payment plan describes the work required to fulfil it. Execution legs keep collection, FX and payout connected instead of collapsing them into a single success flag.
Controlled execution
State machines and idempotency govern execution. Each attempt has a recorded outcome, and a network timeout is treated as an unknown result that needs investigation.
- Keep the original instruction distinct from each execution attempt.
- Check provider status and existing evidence before retrying an uncertain operation.
- Apply configured routing, limits, permissions and approval requirements.
A common contract for money rails
Rail adapters translate provider-specific interactions into the common model. Their capabilities describe what a connected provider can do; payout and collection operations use the matching capability contracts.
APIs, verified callbacks, statement files and transaction-source connections supply the records needed to understand execution and settlement. Credentials and partner configuration stay outside the common contract.
Read the Rail Adapter ContractOne financial ledger
Execution events describe what happened. The double-entry ledger records the financial effect. Keeping both connects an operational action to the balances and positions it changed.
The event history and the references from each posting to its payment, execution and source evidence are preserved. Corrections carry an explanation and a traceable record.
Independent reconciliation
The reconciliation engine compares internal records with partner settlement reports, bank statements and other agreed evidence. A provider response alone is not proof that the financial lifecycle is complete.
Differences become exceptions with their supporting records. Agents help investigate and draft explanations, while permissions and the approval model govern financial decisions.
Explore Flominzo ReconExplainable financial closure
Financial closure means the required records have been reconciled and outstanding differences resolved under the agreed rules. The decision keeps its evidence and explanation.
Later bank records or adjustments can change that conclusion. Reopening preserves the earlier decision and shows the new evidence instead of silently rewriting history.
Built to be trusted
Agents propose. Controls decide.
Agents interpret, investigate and explain. Mandates, permissions, state machines and financial evidence decide what happens to money, and every decision carries its author.
Explore securityAgents propose,
never executeMandates and limits
on every paymentAppend-only
evidencePeople approve
what moves money
Integration
Your systems stay.
Flominzo connects them.
No rip and replace. Our team connects Flominzo to what you run today, however legacy or fragmented, and proves one flow with you before anything else changes.
- Integrate once. Every provider sits behind one Rail Adapter contract, so a new provider changes one adapter, never your core. Rail Adapter Contract
- Start alongside what runs today. Reconciliation reads your existing sources and evidence while current workflows keep running.
- Go live one flow at a time. One payment flow or one reconciliation challenge, mapped and validated with you. Explore the REST API