Clearing is one of the most misunderstood stages in the payment lifecycle. Most merchants know that authorizations happen at checkout and that funds eventually land in their bank account — but the clearing step in between is where the actual accounting work takes place. Understanding clearing helps you manage cash flow timing, reduce chargebacks, and diagnose settlement delays before they become costly problems.
How Clearing Works
After a customer's card is authorized at the point of sale, the transaction does not immediately move money. Instead, the transaction data sits pending until the merchant submits it for clearing, usually through a daily batch. The card network then acts as the central hub, routing and reconciling that data between the acquirer and the card issuer.
Merchant submits batch
At the end of the business day (or on a configured schedule), the merchant's payment system submits all pending authorized transactions as a batch file to the acquiring bank. Each record contains the transaction amount, authorization code, card details, and merchant category code.
Acquirer forwards to card network
The acquiring bank formats the batch data according to card network specifications and transmits it to Visa, Mastercard, or the relevant scheme. The network validates each transaction against its own authorization records.
Card network routes to issuers
The card network disaggregates the batch and routes each transaction to the appropriate card-issuing bank. The issuer verifies the transaction against the original authorization hold and confirms the amount is within tolerance.
Net positions calculated
The card network calculates the net amounts owed between all participating banks for that clearing cycle. Interchange fees are assessed at this stage, reducing the gross transaction amount to determine the net funds to be settled.
Clearing file confirmed
The card network sends confirmation back to the acquirer that transactions have cleared. The settlement process then begins, moving actual funds — typically completing one business day after clearing.
Why Clearing Matters
Clearing is not a back-office technicality — it directly affects how quickly merchants receive funds and how vulnerable they are to disputes. A misconfigured batch or a delayed submission can cost real money.
Visa and Mastercard each process clearing files multiple times per day, handling billions of dollars in transactions. According to the Federal Reserve's Payments Study, US card networks cleared over 50 billion transactions in a single year, with the vast majority settling within two business days. The global real-time payments infrastructure is growing, but for standard card transactions, clearing windows remain the primary determinant of settlement timing.
Research from Mercator Advisory Group found that authorization-to-clearing mismatches — where the cleared amount differs significantly from the authorized amount — account for a measurable share of first-party fraud disputes. Keeping cleared amounts within card network tolerances (typically ±20% of the original authorization for most merchant categories, and ±25% for restaurants and hotels) is not optional: exceeding these thresholds can result in the transaction being rejected at clearing entirely.
Authorization Expiry Window
Most card networks require merchants to clear a transaction within 7 days of the original authorization. After that window, the authorization expires and the transaction will fail to clear, meaning the merchant loses the sale even though the customer was charged a temporary hold.
Clearing vs. Settlement
Clearing and settlement are frequently conflated, but they are distinct stages with different participants, timelines, and outcomes.
| Dimension | Clearing | Settlement |
|---|---|---|
| What happens | Transaction data is exchanged and reconciled | Actual funds move between banks |
| Who is involved | Card network, acquirer, issuer | Acquirer, issuer, central bank / payment rails |
| Timing | 1–2 business days after batch submission | 1 business day after clearing |
| Output | Confirmed net positions and interchange calculations | Funds credited to merchant account |
| Errors surface here | Mismatched amounts, expired authorizations | Insufficient issuer funds, bank routing errors |
| Merchant visibility | Usually none — handled by acquirer | Deposit appears in bank account |
The key takeaway: clearing is the calculation, settlement is the payment. Both must succeed for a merchant to receive funds.
Types of Clearing
Not all clearing works identically. The mechanism depends on the card type, network, and whether the transaction is domestic or cross-border.
Batch clearing is the standard model for credit cards and signature debit. Merchants accumulate transactions and submit them in a single batch processing file, typically once per day. This is the most common model for ecommerce and retail.
Real-time clearing is used by PIN debit networks (NYCE, Star, Pulse) and emerging real-time payment rails like RTP and FedNow. These systems clear and settle in seconds rather than days, though they are currently limited in scope compared to traditional card rails.
Multilateral netting is how card networks handle clearing at scale. Rather than settling each transaction bilaterally, the network calculates a single net position for each member bank across thousands of transactions, dramatically reducing the volume of actual fund transfers required.
Cross-border clearing adds a foreign exchange conversion step and may route through correspondent banking relationships, extending the clearing timeline and adding FX spread costs on top of interchange.
Best Practices
For Merchants
Submit your daily batch as early as possible to maximize the chance of clearing within the same processing window. Avoiding late-night submissions reduces the risk of hitting cut-off times that push transactions to the next business day's clearing cycle.
Always clear the exact amount the customer agreed to pay. If the final amount differs from the authorization — for example, after adding tips in a restaurant or adjusting quantities in an order management system — ensure the delta falls within your card network's allowed tolerance for your merchant category code. Keep a record of authorization codes and match them to your clearing file before submission.
Monitor your batch rejection rate. Most acquirers provide a clearing exception report; a rejection rate above 1–2% is a signal that your integration or batch formatting has a systematic problem worth investigating.
For Developers
Implement idempotent batch submission logic so that network timeouts or system failures do not result in duplicate clears. A transaction cleared twice will trigger an immediate chargeback from the issuer.
Respect the authorization expiry window at the code level. Store the authorization timestamp alongside each transaction and build logic that flags authorizations approaching the 7-day limit so they can be submitted immediately or voided cleanly.
When integrating with multiple acquirers, normalize your clearing data format to each acquirer's specification rather than assuming a single format works universally. Field ordering, date formats, and amount encoding can differ between acquirer APIs, and a malformed field silently causes clearing failures that are difficult to diagnose.
Common Mistakes
Submitting batches after authorization expiry. Waiting too long to close a batch — common during holiday shutdowns or system outages — means authorizations expire before clearing. The transaction fails, the customer's hold releases, and the merchant receives no funds despite the original approval.
Clearing a different amount than authorized. Merchants sometimes adjust order totals after authorization (substituted items, added shipping fees) without understanding that clearing an amount outside tolerance will cause a rejection. Always re-authorize if the final amount changes significantly.
Conflating authorization declines with clearing failures. A transaction can be authorized but fail to clear if the batch data is malformed or the authorization code is entered incorrectly. Monitoring only authorization success rates misses an entire failure category that erodes revenue silently.
Ignoring clearing exception reports. Most acquirers provide daily exception files showing which transactions were rejected during clearing. Merchants who do not review these reports lose revenue that could be recovered by re-submitting corrected transactions within the allowable window.
Using a single acquirer with no redundancy. If your acquirer experiences a clearing outage, all pending transactions are delayed or lost. Payment orchestration platforms that route across multiple acquirer connections provide automatic failover so clearing continues even if one processor is down.
Clearing and Tagada
Tagada is a payment orchestration platform that sits between your application and multiple acquirers, giving you centralized control over how transactions flow through clearing across your entire payment stack.
With Tagada, you can configure automatic batch submission timing per acquirer, set alerts when your clearing rejection rate exceeds a threshold, and route retry logic for failed clears to a backup acquirer — all without changing your integration code. This is particularly valuable for merchants operating across multiple geographies where clearing windows and acquirer cut-off times vary significantly.