Use Case

Three-Way Transaction Matching Architecture & Guide | NAYA

Automate 3-way financial matching between internal orders, payment gateway clearing feeds, and raw bank settlement statements with NAYA.

Automated Three-Way Transaction Matching at Scale

Two-way matching leaves critical blind spots between processor fees and bank settlement amounts. The NAYA Proof Engine automates multi-way triangular reconciliation across all three sources: internal orders, processor settlement files, and raw bank statements.

High-velocity fintechs, marketplaces, and e-commerce platforms process millions of transactions monthly across diverse payment methods. When payments settle, gross capture amounts rarely match the net lump-sum deposits that appear on bank statements.

NAYA replaces spreadsheet-based matching with deterministic multi-identifier reconciliation, verifying that every transaction intent turns into cleared processor settlement and verified cash in the bank.

The Three-Way Financial Data Matrix

Triangulate the three authoritative sources of truth to achieve complete financial control:

  1. Internal Order Database (Intent): The operational system record capturing what the user purchased, customer identity, authorization timestamps, and expected amounts.
  2. Payment Processor Settlement Reports (Clearing): Gateway clearing files (from Stripe, Adyen, Checkout.com, Braintree) documenting gross captured amounts, interchange fees, network assessments, and batch payout identifiers.
  3. Raw Bank Statement Feeds (Cash Realization): BAI2, MT940, or ISO 20022 bank statements confirming the exact net cash deposited into corporate or custodial bank accounts.

Handling Net Deposits and Processor Fee Deductions

3-way matching breaks down when payment processors deduct blended interchange fees before batch-depositing net funds into the bank.

NAYA correlates gross order records, gateway fee logs, and net bank deposits into unified triangular proof units:

  • Gross-to-Net Math Reconstruction: Automatically isolate per-transaction fixed fees, percentage basis points, interchange spreads, and refund holdbacks.
  • N:M Batch Settlement Matching: Link single lump-sum bank deposits against thousands of individual card authorizations and gateway charge records.
  • Multi-Currency and FX Transparency: Match foreign currency transactions against localized settlement bank accounts with exact conversion rate attribution.

Deterministic Matching Rules and Exception Flagging

Apply deterministic matching logic across unique gateway transaction IDs, bank reference numbers, and timestamp windows, routing partial matches and unverified fees to exception workflows.

  • Deterministic Multi-Key Matching: Match on processor transaction IDs, authorization codes, order numbers, and settlement timestamps.
  • Automated Break Categorization: When variances occur, NAYA automatically classifies whether the break is caused by timing delays, processor fee adjustments, or chargeback debits.
  • Exportable Proof Packs: Every completed reconciliation cycle produces a cryptographically signed Proof Pack for partner banks, auditors, and regulatory examiners.

Learn more about our core matching capabilities in the NAYA Proof Engine or explore how we streamline operational ledgers in Operational Ledger.

Frequently Asked Questions

QWhat is three-way financial transaction matching?

Three-way matching reconciles three distinct financial records: internal order/ledger data (transaction intent), payment processor settlement files (clearing records), and raw bank statement feeds (actual cash realization).

QWhy does two-way matching fail in modern payment processing?

Two-way matching ignores the spread between gross order amounts and net bank deposits created by processor interchange fees, refunds, and rolling reserve deductions, leaving blind spots.

QHow does NAYA automate three-way matching?

The NAYA Proof Engine normalizes data across all three sources, performs deterministic N:M graph matching, reconstructs fee math, and isolates breaks in real-time exception queues.

Get technical insights weekly

Join 4,000+ fintech engineers receiving our best operational patterns.