All articles
Card-Linked OffersFintechPayments TechOpen Banking

Dual-Message Clearing: Solving Real-Time CLO Settlement

The Reward Collection

Explore the technical infrastructure behind CLO settlement, from dual-message clearing and tip adjustments to real-time merchant descriptor sanitisation.

For consumer-facing banking apps, the magic of a Card-Linked Offer (CLO) appears instantaneous: a cardholder taps their debit or credit card at an independent bistro or high-street store, and within seconds, a mobile notification sounds: “You've earned £4.50 cashback with The Reward Collection.”

Yet beneath that millisecond mobile event lies one of the most intricate engineering puzzles in fintech. Card payments do not settle in real time. Instead, card-linked reward platforms operate across complex payment scheme rails governed by dual-message clearing protocols, volatile pre-authorisation holds, gratuity adjustments, and unstructured point-of-sale (POS) metadata.

Building enterprise-grade banking loyalty infrastructure requires an architecture capable of reconciling real-time consumer psychology with the asynchronous, delayed reality of global payments clearing. Here is a technical breakdown of how modern CLO networks solve this challenge.

The Dual-Message Dilemma: Authorisation vs Presentment

Most modern retail card transactions rely on the dual-message system (predominantly across Visa and Mastercard credit and debit networks). Unlike single-message networks (often found in domestic ATM networks or specific PIN-debit architectures where clearing and settlement occur simultaneously), dual-message transactions split processing into two separate stages:

  1. Authorisation (Auth Message): Sent in real time (within 100–300 milliseconds of the card tap) via an ISO 8583 or ISO 20022 message. The issuer verifies available credit or balances, checks fraud parameters, places an active reservation (hold) on the funds, and returns an approval code.
  2. Presentment and Clearing: Transmitted hours or sometimes days later. The merchant's acquiring bank batches completed transactions and submits them to the card scheme for formal financial clearing, currency conversion, and fund settlement.

This structural gap presents a formidable challenge for CLO infrastructure.

If a loyalty engine relies solely on real-time authorisation webhooks to disburse cashback, it risks funding rewards on transactions that are later reversed, voided, or altered. Conversely, if the platform waits until final clearing files settle 48 hours later to acknowledge the reward, the psychological reinforcement of the card-linked experience evaporates.

Modern infrastructure solves this by decoupling the notification lifecycle from the financial settlement lifecycle. The authorisation payload triggers an immediate provisional reward notification within the consumer's banking interface. The actual cash disbursement, ledger reconciliation, and merchant invoicing remain locked in pending status until the corresponding clearing record matches the authorisation token.

Edge Cases: Tip Adjustments, Pre-Auths, and Split Tenders

In hospitality and service verticals, the final settled amount rarely matches the initial authorisation string. A diner might authorise a bill for £80.00 at 20:30 on a Friday evening. Half an hour later, a discretionary 12.5% gratuity is added, updating the final merchant batch claim to £90.00.

Handling these edge cases requires stateful event processing engines capable of navigating multiple edge states:

  • Tip and Gratuity Adjustments: In hospitality, the initial auth hold excludes tips. If a cardholder has an offer requiring a £85 minimum spend, an initial £80 auth would evaluate as ineligible. The loyalty rules engine must listen for settlement variance and re-evaluate threshold qualification dynamically upon presentment.
  • Automated Fuel Dispensers (AFD) & Pre-Auth Holds: Pay-at-pump fuel terminals routinely place a standard pre-authorisation hold (frequently £100 or £120) before fuel is dispensed. The consumer may only dispense £35 of fuel. The CLO network must suppress naive threshold notifications triggered by the temporary hold, resolving the reward strictly against the subsequent reversal-and-clearing value.
  • Foreign Exchange (FX) Drift: For cross-border shopping, currency exchange rates fluctuate between Friday night authorisation and Tuesday morning clearing. Reward engines must anchor cashback rules to the settled base currency amount to prevent merchant margin exposure.

Without hardened reconciliation mechanisms, loyalty programmes either bleed capital through false-positive payouts or alienate consumers through missing rewards.

Descriptor Sanitisation: Parsing Messy POS Metadata

Perhaps the most demanding technical layer in CLO infrastructure is merchant resolution. When a cardholder transacts at a retail location, the merchant descriptor string passed inside the transaction payload is notoriously unstructured.

Rather than receiving clean data, the card network receives cryptic, truncated strings such as:

TST* SQ *COFFEE-ROAST_SHOREDITCH_LON_GB_XXXX8472

To match this auth event to a contracted merchant partner in the network, the ingestion engine must normalise, clean, and enrich the transaction data at wire speed.

[Raw Card Auth Payload] 
       │
       ▼
[Regex Cleaning & Strip POS Artifacts] ──> Removes 'SQ *', terminal IDs, location codes
       │
       ▼
[Deterministic Entity Matching] ─────────> Matches normalised name to Merchant DB
       │
       ▼
[Enrichment & Geo-Verification] ─────────> Validates MCC + Postal Code coordinates
       │
       ▼
[Rules Evaluation Engine] ───────────────> Applies user tier, margin logic, spend cap
       │
       ▼
[Provisional Ledger Entry] ──────────────> Dispatches real-time banking app push alert

This pipeline cleans punctuation and terminal artefacts, parses Merchant Category Codes (MCCs), and matches acquiring identifiers against validated merchant registries. At The Reward Collection, our infrastructure links over 500 established retail merchants with financial institutions, parsing millions of transaction records with deterministic accuracy to prevent false attributions and ensure every qualifying spend triggers seamlessly.

Settlement Ledgering and Reconciliation Architecture

Once the presentment file clears, the loyalty network initiates its financial ledgering workflow. Unlike consumer voucher engines that operate on speculative clicks, card-linked rewards function on closed-loop, verifiable financial data.

To ensure enterprise-grade accountability, platforms implement double-entry ledgers:

  1. Provisional Hold Creation: Upon successful auth parsing, a provisional credit entry is generated in the consumer's loyalty ledger, balanced by an accrued liability against the campaign budget.
  2. Presentment Matching: When the clearing file arrives, the clearing transaction is matched via the scheme network reference ID or tokenised card PAN identifier. The provisional state graduates to a confirmed earn.
  3. Reversals and Returns Handling: If a cardholder returns an item for a refund 14 days later, a negative clearing file arrives. The reconciliation engine must accurately identify the historical linked reward and issue a clawback or ledger debit, preventing return-fraud exploitation.
  4. Invoicing and Clearing: At the end of the billing period, consolidated clearing reports are generated. The merchant is invoiced strictly for verified, net-of-returns sales, while the banking partner distributes the earned cashback straight into customer current accounts.

For more technical insights into our API integrations and ledger reconciliation protocols, explore our frequently asked questions.

Building Resilient Infrastructure for Modern Financial Institutions

Card-linked technology operates at the vital intersection of high-volume payment processing, big data normalisation, and real-time mobile UX. The infrastructure must be robust enough to handle weekend peak throughput during holiday trading, agile enough to parse chaotic transaction descriptors, and compliant enough to satisfy bank-grade financial auditing.

By handling the intricacies of dual-message clearing, tip reconciliation, and string sanitisation behind clean API endpoints, The Reward Collection removes technical friction for retailers and financial institutions alike. Instead of wrestling with raw ISO payment streams, banking partners can deliver instant, delightful card-linked incentives that drive verified primary card stickiness.

Are you looking to scale your reward infrastructure or connect your card portfolio to a high-liquidity merchant network? Explore how our platform operates, or reach out to our engineering team to discover how we architect next-generation loyalty experiences.

Ready to power your loyalty programme?

Connect with the UK's leading Card-Linked Offers and Open Banking network.

Get Connected →