FINANCIAL INFRASTRUCTURE FOR CONNECTED ECONOMIES

Dubai · Bengaluru | Trust Center ↗

Insights/Reconciliation Payment Platform Design

Why Reconciliation Should Be Designed with the Payment Platform - Not After Go-Live

Why reconciliation and settlement architecture should be designed at the same time as payment processing.

Many payment platforms are initially designed around one objective:

  • Make the transaction work.

  • Customer initiates payment. The provider processes it. The merchant receives confirmation.

Then finance teams ask a different question:

Where exactly did the money go?

That is when reconciliation problems begin.

A successful API response is not financial settlement

  • A transaction may pass through multiple systems before funds are finally settled.

  • Each participant may maintain its own transaction identifier, timestamps, fees and statuses.

  • A payment marked successful in one system may appear differently in another.

  • Reversals, timeouts, retries and delayed callbacks complicate the picture further.

  • Reconciliation exists to establish whether operational transaction records agree with the financial records of the parties involved.

Design transaction identity from day one

  • Every transaction should have traceable identifiers across the lifecycle.

  • Internal references, partner references, external network references and settlement references should be preserved rather than overwritten.

  • Idempotency should prevent retry behaviour from unintentionally generating duplicate financial transactions.

  • Transaction state changes should also be auditable.

  • These appear to be technical design details until a finance team must investigate a missing settlement.

  • Then they become financial-control requirements.

Model fees and settlement explicitly

  • Payment platforms should understand more than gross transaction value.

  • Processor fees, commissions, taxes, revenue shares, merchant deductions and settlement adjustments may all affect the final amount.

  • Reconciliation architecture should therefore support multiple levels of matching.

  • Transaction-level reconciliation establishes whether individual records agree.

  • Settlement-level reconciliation establishes whether aggregate financial obligations have been fulfilled.

Exception management matters

  • No payment environment reconciles perfectly forever.

  • Files arrive late. Provider references change. External services experience delays. Refunds cross settlement periods.

  • A good reconciliation platform therefore does not simply identify matched transactions.

  • It manages the unmatched ones.

  • Operations teams need queues, ageing, assignment, investigation, comments, adjustments, maker-checker controls and audit trails.

Design financial operations alongside payments

  • When reconciliation is added after go-live, teams often discover that transaction data does not contain everything required for matching.

  • Correcting the architecture later can be expensive.

  • UNIPHI’s approach is therefore to treat payment processing, reconciliation and settlement as connected components of the same financial lifecycle.

  • A payment is not operationally complete simply because it has been processed.

  • It is complete when the institution can account for it.

Build the financial infrastructure behind your next digital product

UNIPHI brings together digital banking, wallets, payments, lending, cards, remittances, agency banking, reconciliation, identity, risk and embedded finance through a modular technology platform.