Payment Settlement Explained: How Money Actually Moves Between Banks

You tap your card, the terminal says “Approved,” and you walk out with your coffee. But here’s the thing — no money has actually moved yet. The merchant won’t see a single cent for hours, sometimes days. What happens in between is the invisible machinery of settlement and clearing.

What is Payment Settlement?

Payment settlement is the process by which funds are actually transferred from the cardholder’s bank (the issuer) to the merchant’s bank (the acquirer) to fulfill a card transaction. It is the final step in a three-phase process:

1. Authorization — “Can this card pay?” (real-time, milliseconds)
2. Clearing — “Here’s what happened today.” (batch, end-of-day)
3. Settlement — “Move the money.” (interbank transfer, next business day)

When a developer sees a Response Code: 00 (Approved) in an ISO 8583 message, that’s authorization. The merchant has permission to collect — but the money doesn’t move until settlement completes, typically T+1 (one business day after the transaction).

Look it up: Check the meaning of any response code in our Reference Database — including authorization approvals, declines, and referrals.

Also Known As…

Settlement and clearing terminology varies across the industry:

Authorization vs. Clearing vs. Settlement

These three phases are often confused. Here’s exactly what happens at each stage:

Phase 1: Authorization (Real-Time)

When a card is swiped, dipped, or tapped, the terminal sends an authorization request (MTI 0100) to the issuer via the card network. This happens in under 2 seconds:

Terminal ──▸ Acquirer ──▸ Card Network ──▸ Issuer
                                            │
   "Approved" (RC 00) ◂── ◂── ◂── ◂── ◂───┘

At this point:

• The issuer places a hold on the cardholder’s available balance
• The merchant receives an authorization code (e.g., A12B3C)
• No money moves. This is a promise, not a payment.

Parse it yourself: Use the ISO 8583 Studio to decode authorization request and response messages, including Field 38 (Authorization Code) and Field 39 (Response Code).

Phase 2: Clearing (Batch)

At the end of the business day, the merchant’s terminal or POS system batches all approved transactions and submits them for clearing. This batch message (MTI 0500 series) goes to the acquirer:

Terminal "Batch Close"
   │
   │  Today's transactions:
   │  ┌────────────────────────────────────────────┐
   │  │ Auth Code  │ Amount  │ Card (masked) │ Time │
   │  │ A12B3C     │ $4.50   │ ****1234      │ 7:02 │
   │  │ D45E6F     │ $12.99  │ ****5678      │ 8:15 │
   │  │ G78H9I     │ $3.25   │ ****9012      │ 9:41 │
   │  └────────────────────────────────────────────┘
   │
   ▼
Acquirer Processor

The acquirer then forwards these clearing records to the appropriate card networks (Visa, Mastercard, etc.), which route them to each issuing bank.

Phase 3: Settlement (Fund Transfer)

The card network calculates the net position between all banks and initiates the actual fund transfer:

Card Network Settlement
┌──────────────────────────────────────────────┐
│                                              │
│  Issuer A owes:     $1,200,000               │
│  Issuer A is owed:    $800,000               │
│  ─────────────────────────────               │
│  Net position:       -$400,000 (pays out)    │
│                                              │
│  Acquirer B is owed: $950,000                │
│  Acquirer B owes:    $150,000                │
│  ─────────────────────────────               │
│  Net position:      +$800,000 (receives)     │
│                                              │
└──────────────────────────────────────────────┘

Funds move via the banking system (ACH, Fedwire, or the network’s own settlement bank), and the acquirer deposits the merchant’s share — minus fees — into their bank account.

The T+1 Settlement Cycle

T+1 means settlement occurs one business day after the transaction date. For card payments, this is the most common cycle:

What Counts as “T”?

The transaction date (“T”) is typically the batch close date, not the authorization date. This distinction matters:

Key insight: Weekends and bank holidays are not business days. A Friday transaction typically settles on Monday. A Friday before a holiday weekend may not settle until Tuesday.

Why Not Settle Instantly?

There are practical reasons settlement isn’t real-time:

1. Netting efficiency — Banks process millions of transactions. Settling the net difference is far cheaper than settling each individually.
2. Dispute window — The gap allows for voided transactions, adjustments, and error corrections before money moves.
3. Batch processing — Legacy banking infrastructure processes in daily cycles, not continuously.
4. Time zone coordination — Global networks must reconcile across time zones with a consistent cutoff.
5. Fraud checks — Issuers perform additional risk screening on clearing records before releasing funds.

How Card Networks Handle Settlement

Each card network operates its own settlement system:

Visa: VisaNet Settlement

Visa’s settlement service, VisaNet, processes clearing and settlement globally:

Visa settles in USD by default and uses correspondent banks for currency conversion in cross-border transactions.

Mastercard: Banknet and GCMS

Mastercard’s clearing system uses IPM (Integrated Product Messages) files:

Single-Message vs. Dual-Message Systems

This is a critical architectural distinction:

In a dual-message system, the 0100/0110 authorization is a separate event from the 0200/0210 financial transaction that triggers clearing. In a single-message system, the authorization message itself initiates the fund movement.

MTI reference: Look up message type indicators like 0100, 0200, 0400, and 0500 in our Reference Database to understand the full message flow.

The Interchange Fee: Who Gets Paid

When settlement occurs, the merchant doesn’t receive the full transaction amount. Fees are deducted at each layer:

Customer pays:                   $100.00
                                    │
Interchange fee (issuer keeps):  -  $1.80  (e.g., 1.80%)
Assessment fee (network keeps):  -  $0.13  (e.g., 0.13%)
Acquirer markup:                 -  $0.30  (e.g., 0.30%)
                                    │
Merchant receives:                $97.77

Interchange rates vary dramatically by:

• Card type — Rewards cards cost merchants more than basic debit
• Transaction type — Card-present (CP) is cheaper than card-not-present (CNP)
• Merchant category — Grocery and gas typically have lower rates
• Capture method — EMV chip has lower rates than swiped magnetic stripe

Settlement Data in ISO 8583

Several ISO 8583 fields are directly involved in the clearing and settlement process:

Decode the message: Use the ISO 8583 Studio to parse raw authorization and financial messages. Field 5 (Settlement Amount) and Field 15 (Settlement Date) are particularly important for reconciliation.

Common Settlement Scenarios

Scenario 1: Standard Purchase

Timeline:
Monday 10:00am   Authorization (0100) → Approved (0110, RC=00)
Monday 11:00pm   Batch close — merchant submits clearing file
Tuesday 2:00am   Network processes clearing records
Tuesday 6:00am   Net settlement calculated
Tuesday           Funds transferred (Issuer → Network → Acquirer)
Tuesday 3:00pm   Merchant account funded

Scenario 2: Pre-Authorization and Completion

Hotels and gas stations use pre-authorizations that settle for a different amount:

Friday 3:00pm   Pre-auth $200 (hotel estimated stay)
                → Issuer holds $200 on cardholder account
Sunday 11:00am  Check-out: actual charge $142.50
                → Merchant sends completion for $142.50
                → Issuer releases $57.50 hold difference
Monday          Settlement for $142.50

If the merchant never sends the completion, the authorization hold expires (typically 7-30 days depending on the issuer and merchant category).

Scenario 3: Void Before Settlement

Monday 2:00pm   Authorization for $50.00 — Approved
Monday 2:05pm   Customer changes mind — Void (0400)
Monday 11:00pm  Batch close — void is included in clearing
                → Transaction nets to $0 — no settlement needed
                → Issuer releases the $50 hold immediately

Voids are free for merchants (no interchange fee) because the transaction never enters settlement.

Scenario 4: Refund After Settlement

Monday          Purchase settles for $75.00
Wednesday       Customer requests refund
                → Merchant initiates a credit transaction (0200, Processing Code 20xxxx)
Wednesday 11pm  Refund included in batch close
Thursday        Refund settles — money flows in reverse
                → Acquirer → Network → Issuer → Cardholder

Unlike voids, refunds do incur fees because they create a new settlement transaction flowing in the opposite direction.

Settlement Reconciliation

Reconciliation is the process of matching authorizations to settlements to ensure every approved transaction is funded correctly. This is where most operational headaches occur.

Common Reconciliation Mismatches

Reconciliation Keys

To match an authorization to its settlement record, developers typically use a combination of:

// Primary match: Retrieval Reference Number (Field 37)
// This is the most reliable single-field match
function matchAuthToSettlement(auth, settlement) {
    return auth.field37 === settlement.field37;
}

// Composite match when RRN is missing or recycled
function compositeMatch(auth, settlement) {
    return auth.field38 === settlement.field38  // Auth code
        && auth.field42 === settlement.field42  // Merchant ID
        && auth.field4  === settlement.field4   // Amount
        && dateDiff(auth.field12, settlement.field12) <= 7; // Within 7 days
}

Sanitize before debugging: When sharing settlement reconciliation logs with your team, run them through the PCI Sanitizer to mask PANs and other sensitive data.

Chargebacks: Settlement in Reverse

A chargeback occurs when the issuer reverses a settled transaction, pulling funds back from the merchant. The chargeback process interacts directly with settlement:

Chargebacks are deducted from the merchant’s next settlement batch, reducing their funding. Multiple chargebacks can cause a merchant’s settlement to go negative, triggering a reserve hold or account termination.

Settlement Across Borders

Cross-border transactions add currency conversion to the settlement process:

Cardholder (EUR)                Network               Merchant (USD)
     │                            │                         │
     │  Auth: €85.00              │                         │
     │  ────────────▸             │                         │
     │                            │  Auth: $92.65           │
     │                            │  ──────────────▸        │
     │                            │                         │
     │                 Clearing:  │                         │
     │           EUR→USD @ 1.09   │                         │
     │                            │                         │
     │  Billed: €85.00            │  Settled: $92.65        │
     │  (+ 1% cross-border fee)   │  (- interchange)        │

The Move Toward Faster Settlement

The payments industry is shifting toward faster — and eventually real-time — settlement:

Why T+1 Still Dominates Cards

Despite real-time alternatives, card settlement remains T+1 because:

1. Network economics — Netting saves billions in transfer costs daily
2. Dispute mechanics — Chargeback rights require a settlement delay
3. Global coordination — 200+ countries, thousands of banks, multiple time zones
4. Legacy infrastructure — Decades of batch processing systems
5. Risk management — Delay allows fraud screening on clearing records

Learn more about security: Understand how 3D Secure authentication and payment tokenization work alongside settlement to protect transactions.

Quick Reference: Settlement Timeline

Next Steps

Now that you understand how money actually moves behind every card transaction:

1. Parse authorization messages with the ISO 8583 Studio — see Fields 5, 15, and 37 in action
2. Look up response codes in the Reference Database — understand why transactions decline before reaching settlement
3. Learn about EMV chip data in the EMV Field 55 Guide — the cryptographic data that travels alongside authorization
4. Understand PCI compliance in our PCI DSS Guide — the security standards governing transaction data throughout the settlement lifecycle
5. Explore key management with our DUKPT Guide — how encryption keys protect card data from terminal to settlement
6. Compare messaging standards in our ISO 8583 vs ISO 20022 Guide — settlement is where ISO 20022 is already replacing ISO 8583

This post is part of the ISO 8583 Mastery series. Follow along as we explore payment messaging in depth.