Guides
Card payment guide: authorization, capture, clearing, settlement, and disputes
Card payment guide to authorization, holds, capture, clearing, settlement, posting, refunds, and disputes across merchant and issuer records.
What to take away
- Approval at checkout is an authorization, not proof that final settlement has occurred.
- A pending hold and a posted charge are different account states, even when the amounts match.
- The merchant, acquirer, network, issuer, and processor may each hold a different reference for one purchase.
- A refund, authorization release, reversal, billing-error notice, and chargeback are not interchangeable.
- Preserve the receipt, descriptor, dates, amounts, and communications before choosing a remedy.
A card purchase feels instant because the customer receives an answer at the terminal or checkout page. Behind that answer is a sequence of messages and accounting events. The stages can happen seconds or days apart, and each participant may label them differently.
Understanding the sequence helps a customer investigate an unfamiliar entry and helps a merchant reconcile sales without confusing a hold with collected money. This guide covers the common U.S. card-payment model. Contract terms, network rules, card type, and applicable law can change the result.
The participants in a typical purchase
The cardholder presents a card or credential to a merchant. The merchant sends transaction data through a gateway or processor to its acquiring institution. A card network routes the request to the issuer, which decides whether to approve or decline it.
| Participant | Main job in the transaction |
|---|---|
| Cardholder | Uses the card and is responsible under the account terms |
| Merchant | Supplies the goods or services and submits the transaction |
| Acquirer | Contracts for merchant acceptance and receives merchant transactions |
| Processor or gateway | Transmits, formats, screens, or records payment messages |
| Network | Routes messages under its operating rules |
| Issuer | Provides the card account and approves or declines requests |
Names can overlap. A bank may issue cards and acquire merchant transactions. A processor may serve several participants without owning the customer account.
Federal Regulation II defines an issuer, payment-card network, merchant acquirer, and network processing roles. Those card-system definitions are useful for mapping participants, but they do not prove which firm performed a role in a particular purchase. Confirm the real parties from the card agreement, merchant-services contract, terminal records, and statements.
Stage 1: credential presentation
The customer may insert a chip card, tap a card or device, swipe a magnetic stripe, type card details online, or provide credentials to a merchant that already stores them. The method affects the data and authentication available, but it does not by itself decide whether a later dispute is valid.
Card-present and card-not-present describe the acceptance setting. They do not describe when the customer receives goods, whether the issuer will approve, or whether the merchant will win a later chargeback.
Stage 2: authorization
The merchant requests approval for an amount. The request may include merchant information, card data or a token, transaction type, amount, location indicators, and fraud-control data. The issuer checks the account and its controls, then returns an approval or decline response.
An approval means the issuer authorized the request under the information available at that moment. It does not guarantee final payment in every circumstance, confirm customer satisfaction, or resolve later fraud and billing claims.
Why the amount can be estimated
Hotels, vehicle rentals, fuel dispensers, restaurants, and other businesses may not know the final amount at the first request. They may request an estimated authorization, add an incremental authorization, or submit a final amount after service. The permitted process depends on the merchant category, network rules, issuer behavior, and contract.
Stage 3: the hold
An issuer may reduce available funds or available credit after approval. The account interface commonly labels this entry pending. A pending item may disappear, change amount, or become a posted transaction.
A hold is not a second bill. It is also not proof that the merchant has received settlement. When a final purchase posts while an earlier hold remains visible, the account can temporarily look as if it contains two charges. Compare status, dates, and reference details before adding the amounts together.
Stage 4: capture
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 may capture individual purchases or close a batch. Late capture, incorrect amounts, duplicated batches, or mismatched references can cause reconciliation problems. The merchant should retain the order record, authorization response, capture time, batch ID, and final amount.
Stage 5: clearing
During clearing, transaction records move through the relevant processing chain and the participants calculate obligations. The final record may carry information that differs from the initial authorization, including a completed amount, merchant descriptor, tip, currency result, or transaction date.
The purchase date, processing date, posting date, and statement date can therefore differ without proving an error. Investigators should use all four where available.
Stage 6: settlement and merchant funding
Settlement transfers net obligations among participating institutions. Merchant funding is the acquirer's credit to the merchant, often net of fees, adjustments, reserves, refunds, and chargebacks. These events are related but not identical.
The merchant's bank deposit rarely equals one customer's purchase. A deposit may combine many sales and subtract fees or refunds. Reconciliation should move from transaction to batch to processor report to bank deposit, rather than trying to match each gross sale directly to cash.
Posting on the cardholder account
The issuer records the cleared purchase on the cardholder's account. The displayed descriptor may use a legal name, payment facilitator, abbreviated location, or centralized billing label rather than the storefront sign.
For an unfamiliar entry, record:
- Pending or posted status.
- Exact amount and currency.
- Displayed merchant descriptor.
- Purchase, processing, and posting dates.
- Card or wallet identifier shown.
- Any reference or authorization code.
- Matching receipt, email, delivery record, or household purchase.
Do not publish the full card number, security code, or unredacted account statement while seeking help.
Reversals, releases, refunds, and disputes
These events solve different problems.
| Event | What it generally does |
|---|---|
| Authorization release | Removes or allows expiry of an unused hold |
| Authorization reversal | Sends a message that an approved amount will not be completed as planned |
| Refund | Merchant sends money back after a completed purchase |
| Billing-error notice | Consumer invokes an issuer process under applicable account rules and law |
| Chargeback | Issuer-side transaction return through network and acquiring channels |
| Merchant adjustment | Merchant or processor corrects its own transaction record |
A merchant promising a refund does not necessarily cause an unrelated pending authorization to vanish at once. A customer also should not describe every request to an issuer as a chargeback. State what happened and let the issuer identify the correct process.
Choose 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 the receipt, final invoice, tip, tax, currency, and any merchant adjustment. Contact the merchant promptly if it can correct the record. Preserve formal notice deadlines while pursuing an informal fix.
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 for the merchant if delay could affect 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 requested remedy, and each response. The route can depend on card type and facts.
A compact evidence packet
Keep a chronological file containing:
- account screenshot showing status and descriptor;
- receipt, invoice, or order confirmation;
- delivery or cancellation evidence;
- merchant response and case number;
- issuer notice and case number;
- dates, amounts, and transaction references;
- statement on which the item first appeared;
- redacted copies of submitted documents.
Write down what each party said without converting 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 an authorization stage. Capture, clearing, settlement, and merchant funding may follow.
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 status and references before concluding that both are completed charges.
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 other transaction condition.
Which date should I use when investigating?
Keep every available date: purchase, authorization, capture, processing, posting, statement, and notice. Each can answer a different question.
In this guide
- How to read a card transaction record and investigate a chargeCard transaction record steps for reading status, dates, descriptors, amounts, and references, matching evidence, and reporting a disputed charge.
- Debit, credit, prepaid, and charge cards comparedDebit, credit, prepaid, and charge cards compared by funding source, repayment, fees, holds, overspending risk, records, and dispute process.
- Merchant card acceptance and statement review checklistMerchant card acceptance checklist for contracts, security, authorization, capture, refunds, chargebacks, statement fees, reconciliation, and records.
- Holds, tips, recurring charges, card-not-present fraud, and chargeback confusionCard payment problems explained: authorization holds, tips, recurring charges, card-not-present fraud, duplicate entries, refunds, and chargebacks.
- Resolving a duplicate card authorization and posted charge caseDuplicate card authorization case showing how to separate pending holds from posted charges, trace merchant records, preserve deadlines, and close the file.
