Card payment guide: authorization, capture, clearing, settlement, and disputes

What to take away

A card purchase feels instant because the customer gets an answer at the terminal or the checkout page. Behind that answer sits a sequence of messages and accounting events. The stages can land seconds or days apart, and each participant may label them differently.

Knowing the sequence helps a customer read an unfamiliar entry and helps a merchant reconcile sales without mistaking a hold for collected money. This guide covers the common U.S. card model. Contract terms, network rules, card type, and applicable law can change the result.

Who is actually in the transaction

The cardholder presents a card or a stored credential to a merchant. The merchant sends the transaction through a gateway or processor to its acquiring institution. A network routes the request to the issuer, which approves or declines it.

Roles overlap. A bank can issue cards and acquire merchant transactions at the same time. A processor can serve several participants without owning the customer account.

Federal Regulation II defines issuer, payment-card network, merchant acquirer, and network processing roles. Those card-system definitions help you map the players, but they do not prove which firm performed a role in your purchase. Confirm the real parties from the card agreement, the merchant-services contract, terminal records, and statements.

How the credential gets presented

The customer inserts a chip card, taps a card or a device, swipes a magnetic stripe, types card details online, or lets a merchant use credentials it already stored. The method changes what data and authentication are available. It does not by itself decide whether a later dispute is valid.

Card-present and card-not-present describe the acceptance setting only. They say nothing about when goods arrive, whether the issuer will approve, or who wins a later chargeback.

What authorization does and does not promise

The merchant requests approval for an amount. The request carries merchant information, card data or a token, transaction type, and amount. It also carries location indicators and fraud-control data. The issuer checks the account and its controls, then returns an approval or a decline.

An approval means the issuer authorized the request on the information available at that moment. It does not guarantee final payment in every circumstance, confirm customer satisfaction, or settle later fraud and billing claims.

Why the amount can be an estimate

Hotels, vehicle rentals, fuel dispensers, and restaurants may not know the final amount at the first request. They can request an estimated authorization, add an incremental authorization, or submit the final amount after service. What is permitted depends on the merchant category, network rules, issuer behavior, and contract.

The hold on your available balance

After approval, an issuer may reduce available funds or available credit. The account interface usually labels this entry pending. A pending item can disappear, change amount, or become a posted transaction.

A hold is not a second bill, and it is not proof the merchant has been paid. When a final purchase posts while an earlier hold is still visible, the account can look as if it holds two charges. Compare status, dates, and reference details before adding the amounts together.

Capture: the merchant commits

Capture is the merchant's step of confirming that an authorized transaction should proceed for the final amount. Some systems combine authorization and capture for an immediate sale. Others separate them so the merchant can adjust, complete, or cancel the transaction.

A merchant can capture individual purchases or close a batch. Late capture, wrong amounts, duplicated batches, and mismatched references all cause reconciliation problems. Keep the order record, the authorization response, the capture time, the batch ID, and the final amount.

Clearing: the records move

During clearing, transaction records travel through the processing chain and the participants calculate what each owes. The final record can differ from the initial authorization. It may carry a completed amount, a merchant descriptor, a tip, a currency result, or a different transaction date.

The purchase date, the processing date, the posting date, and the statement date can therefore differ without any error. Investigators should use all four where available.

Settlement and merchant funding

Settlement transfers net obligations among participating institutions. Merchant funding is the acquirer's credit to the merchant. It is usually net of fees, adjustments, reserves, and refunds. The two events are related but not identical.

A merchant's bank deposit rarely equals one customer's purchase. A deposit may combine many sales and subtract fees or refunds. Reconcile from transaction to batch to processor report to bank deposit, rather than trying to match each gross sale directly to cash.

What posts on the cardholder account

The issuer records the cleared purchase on the cardholder's account. The descriptor may show a legal name, a payment facilitator, an abbreviated location, or a centralized billing label instead of the storefront sign.

For an unfamiliar entry, write down:

Do not publish the full card number, the security code, or an unredacted statement while seeking help.

Reversals, releases, refunds, and disputes

These events solve different problems.

A merchant promising a refund does not necessarily make an unrelated pending authorization vanish at once. A customer should also not call every request to an issuer a chargeback. State what happened and let the issuer name the correct process.

Choosing the path from the transaction state

If the item is pending

Ask whether the merchant completed, canceled, or never captured it. Ask the issuer what the pending status means and when its hold policy permits release. A pending item may not yet be eligible for the same procedure as a posted item.

If the item posted at the wrong amount

Compare these items:

If the item is unauthorized

Contact the issuer through a verified channel promptly, secure the account, and follow its formal reporting instructions. Do not wait on the merchant if delay could affect your protection or allow more transactions.

If goods or services are the issue

Separate dissatisfaction, non-delivery, cancellation, and fraud. Record what was promised, what was supplied, the remedy you asked for, and each response. The route can depend on card type and on the facts.

A compact evidence packet

Keep a chronological file containing:

Write down what each party said without turning an estimate into a promise. A support agent saying a hold usually falls away in seven days is not the same as a dated correction confirmation.

Common questions

Does an approved transaction mean the merchant has the money?

No. Approval is the authorization stage. Capture, clearing, settlement, and merchant funding may all follow. Until those steps complete, the merchant has a promise, not a deposit.

Why do I see a pending amount and a posted amount?

The final transaction may have posted while an earlier hold is still displayed. Check the status and the references before concluding that both are completed charges. They often collapse into one entry.

Is a refund the same as a chargeback?

No. A merchant initiates a refund. A chargeback is a network-based return process tied to an issuer dispute or another transaction condition. The two follow different clocks and leave different records.

Which date should I use when investigating?

Keep every date you can find, because each answers a different question. Purchase, authorization, capture, and processing dates rarely line up. Posting, statement, and notice dates rarely line up. The one that matters depends on the deadline you are trying to meet.