Category: Transaction Processing

Clearing

Also known as: Clearing process, Transaction clearing

Simply put

Clearing is the set of steps that happen between the moment a payment transaction is agreed upon and the moment money actually moves between the parties' financial institutions. In a card payment, it typically follows authorization and involves exchanging and reconciling the transaction details so the merchant's bank and the cardholder's bank know what is owed. Clearing prepares a transaction for the final movement of funds, which is called settlement.

Formal definition

In banking and finance, clearing encompasses all activities from the time a commitment is made for a transaction until it is settled, including reconciling purchases and sales and preparing the direct transfer of funds between financial institutions (Sources 2, 5). In a card payment context, clearing is generally distinct from authorization (a real-time approval decision) and from settlement (the actual funds transfer): during clearing, the acquirer and issuer exchange and reconcile transaction data through the relevant card network so that interbank obligations can be calculated. Card-network clearing should be distinguished from clearing on other payment rails such as ACH or checks, which follow different rules, timing, and file-exchange mechanisms; the specific operational and netting arrangements vary by network and rail. Clearing houses and central counterparties may net multiple transactions to reduce the number and value of settlement transfers, though the precise netting and central-clearing mechanisms differ by system and are governed by the rules of each network or clearing organization. Note that several unrelated uses of the word 'clearing' exist outside payments (Sources 1, 3, 4) and are out of scope for this term.

Why it matters

Clearing is the connective step that turns an approved transaction into an actual obligation between banks. Without it, an authorization is only a promise to pay: the issuer has reserved funds, but the merchant's acquirer and the cardholder's issuer have not yet exchanged and reconciled the transaction details needed to calculate what is owed. Understanding clearing as separate from authorization and settlement matters because errors, disputes, and reconciliation problems frequently arise in this middle phase, where transaction data is exchanged through the card network rather than in the real-time approval decision or the final funds transfer.

Clearing also matters because its mechanics differ significantly across payment rails. Card-network clearing follows the file-exchange formats, timing, and netting arrangements set by each card network, whereas ACH and check clearing operate under entirely different rules, timing windows, and file-exchange mechanisms. Teams that treat all clearing as interchangeable risk misjudging when funds actually move, how disputes are handled, and how interbank obligations are calculated. Because clearing houses and central counterparties may net multiple transactions to reduce the number and value of settlement transfers, the value that ultimately settles is not always a simple sum of individual transactions.

Because the precise netting and central-clearing mechanisms differ by system and are governed by the rules of each network or clearing organization, professionals should confirm operational details against the specific network or rail involved rather than assuming uniform behavior. Exact timing, netting arrangements, and reconciliation obligations vary, and treating them as fixed can lead to reconciliation gaps and disputed settlements.

Who it's relevant to

Payment Processors and Acquirers

Acquirers exchange and reconcile transaction data with issuers through the card network during clearing so that interbank obligations can be calculated. Processors need to understand how clearing sits between authorization and settlement, and how netting arrangements affect the value ultimately transferred, because these mechanics vary by network and rail.

Merchant Risk and Reconciliation Teams

These teams rely on accurate clearing data to reconcile what a merchant is owed against what settles. Because clearing is where transaction details are exchanged and reconciled, discrepancies, disputes, and timing differences frequently surface here, and card-network clearing behaves differently from ACH or check clearing.

Compliance and Operations Staff

Staff overseeing payment operations should distinguish clearing from authorization (a real-time approval) and settlement (the actual funds transfer), and confirm timing and netting details against the specific network or clearing organization's rules rather than assuming uniform behavior across rails.

Inside Clearing

Clearing message exchange

The exchange of transaction data between the acquirer and the issuer, typically routed through the card network, that presents the merchant's captured transactions for the issuer to post against the cardholder account. Clearing follows authorization and precedes or accompanies settlement; the data exchanged is transaction-level financial detail rather than the authorization approval itself.

Relationship to authorization and settlement

Clearing is a distinct phase from authorization (the real-time approval or decline) and from settlement (the actual movement of funds between institutions). A cleared transaction has been presented for posting but funds movement is completed in settlement. Practitioners should not treat authorization, clearing, and settlement as a single step.

Netting and clearing-house mechanisms

Many payment systems reduce the number of individual interbank payments by netting obligations among participants so that only net positions are settled, often through a central clearing house or the card network acting as an intermediary. Netting affects settlement amounts and timing but does not by itself change the transaction-level detail carried in clearing records.

Differences across payment rails

Card-network clearing (governed by card brand and network rules) differs from clearing on other rails such as ACH or checks. ACH clearing operates in batches through an automated clearing house on its own scheme rules and timelines, while check clearing involves image or physical presentment. Clearing behavior, timing, return/reversal handling, and dispute processes vary by rail and are set by the governing scheme or network rather than being uniform across all payments.

Data carried in clearing records

Clearing records may contain cardholder data such as the PAN, and any handling, transmission, or storage of that data falls within PCI DSS scope. Sensitive authentication data (full track data, CAV2/CVC2/CVV2/CID, PINs and PIN blocks) must not be stored after authorization even when encrypted, and should not persist into clearing storage. Truncation, masking, tokenization, or encryption may reduce exposure, but their effect on scope depends on implementation and validation, not on the label alone.

Common questions

Answers to the questions practitioners most commonly ask about Clearing.

Is clearing the same as settlement?

No. Clearing and settlement are distinct steps that are often conflated. Clearing is the exchange and reconciliation of transaction information between the acquirer and issuer (typically via the card network) after authorization, establishing the amounts each party owes. Settlement is the subsequent movement of funds to discharge those obligations. Clearing prepares and validates the transaction data; settlement transfers the money. The two are sequenced and related but are not interchangeable terms.

Does clearing mean the transaction has already been approved and the funds guaranteed?

Not exactly. Authorization is the earlier step where the issuer approves or declines and may place a hold on funds; clearing occurs afterward when transaction details are submitted and reconciled to determine what is actually owed. Clearing does not by itself guarantee final funds movement, and it does not eliminate the possibility of later disputes or chargebacks, which are governed by card brand and network rules that vary by region and change over time. Whether and when funds are considered final depends on the settlement process, not on clearing alone.

How does clearing on the card networks differ from clearing on other payment rails like ACH or checks?

The general concept of exchanging and reconciling transaction information before funds move applies across payment rails, but the mechanics differ by system. Card-network clearing follows the network's own operating rules, formats, and timelines for exchanging transaction records between acquirers and issuers. ACH and check clearing operate under different rule sets, operators, and file exchange processes. Because each rail has its own governance, formats, and timing, controls and reconciliation designed for card clearing should not be assumed to apply unchanged to other rails; confirm the specific rules for the rail in question.

How are clearing obligations combined across many transactions, and what role does netting play?

Rather than moving funds for every individual transaction, many systems aggregate obligations and calculate net positions between parties, so that only the net amounts owed are settled. Card networks and central clearing arrangements commonly use such netting to reduce the number and volume of funds transfers. The exact netting mechanism, cycle timing, and which parties are netted against one another are defined by the applicable network or clearing-house rules, which vary by system and region and can change; confirm the current rules for your environment rather than assuming a fixed model.

What data is exchanged during clearing, and does that create PCI DSS scope considerations?

Clearing records typically carry transaction details needed for reconciliation, which may include cardholder data such as the PAN. Sensitive authentication data—including full track data, card verification values (CAV2/CVC2/CVV2/CID), and PINs or PIN blocks—must not be stored after authorization, even when encrypted, so it should not be retained in clearing files or logs. Where the PAN or other cardholder data is present in clearing systems, those systems may fall within PCI DSS scope. Whether techniques like tokenization, truncation, or masking reduce that scope depends on the specific implementation and validation, not on the label alone; confirm requirements against the current published PCI DSS.

How should teams reconcile clearing records against authorization and settlement data?

Reconciliation generally involves matching authorization records to the corresponding clearing records and then to settlement outcomes, so that discrepancies—such as amount differences, missing records, or duplicates—are identified and investigated. Because clearing establishes the amounts owed and settlement moves the funds, differences between these stages are a common point to monitor. Handle any cardholder data in these records under defined controls, ensure sensitive authentication data is not retained, and follow the specific file formats, timing, and dispute windows defined by the applicable network or rail rules, confirming the current rules for your region and environment.

Common misconceptions

Clearing is the same as authorization, so an approved transaction is already cleared and settled.

Authorization is a real-time approval or decline that reserves funds or confirms availability; clearing is the later presentment of transaction detail for posting, and settlement is the actual movement of funds. These are separate phases with distinct data flows and timing.

Clearing works the same way across all payment types, whether card, ACH, or check.

Clearing mechanics, timing, netting, and return handling differ by rail. Card-network clearing follows card brand and network rules, ACH follows automated clearing house scheme rules on a batch basis, and check clearing uses presentment processes. The governing scheme determines behavior, and these rules change and can vary by region.

Clearing records only contain amounts, so they are outside PCI DSS scope.

Clearing records commonly carry cardholder data such as the PAN, which places their transmission, processing, and storage within PCI DSS scope. Sensitive authentication data must not be retained after authorization, and any scope reduction from tokenization, truncation, masking, or encryption depends on how it is implemented and validated.

Best practices

Model authorization, clearing, and settlement as distinct phases in system and data-flow diagrams, and confirm which cardholder data elements exist at each phase against the current published PCI DSS rather than assuming a fixed requirement number.

Identify the payment rail for each flow (card network, ACH, check) and apply the clearing, netting, timing, and return rules of the governing scheme, since these differ by rail and can vary by region.

Verify that no sensitive authentication data (full track data, CAV2/CVC2/CVV2/CID, PINs or PIN blocks) persists into clearing or settlement storage after authorization, even in encrypted form.

Apply truncation, masking, tokenization, or encryption to PANs in clearing records where feasible, and validate the actual scope impact of each approach instead of relying on the control's label.

Reconcile cleared transactions against authorizations and against settled amounts, accounting for netting so that net settlement positions can be traced back to individual transaction-level clearing detail.

Track changes to card brand, network, and other scheme rules that govern clearing, dispute, and return timelines, and update reconciliation and exception handling accordingly.