Authorization vs Capture: From Approval to Payout (2026)

Authorization vs capture is the split between approving a card payment and collecting it. Authorization is the issuer’s real-time approval, which places a hold on the cardholder’s funds. Capture is the merchant’s later instruction to charge the final amount, which sends the transaction into clearing, settlement and, finally, funding to the merchant.

In 2026, the gap between the two steps is regulated more tightly than ever. Card schemes set how long an authorization stays valid, charge fees when holds are left open, and let issuers dispute payments captured too late. For PSPs, PayFacs and platforms, authorization and capture rules decide how they handle rentals, pre-orders, marketplaces and split shipments, and when their merchants actually see the money.

What is the difference between authorization and capture?

Authorization asks “can this card pay this amount?”; capture says “now charge it”. The first is a message exchanged in seconds between the merchant’s acquirer, the card scheme and the issuer. The second is the merchant’s confirmation of the final amount, sent later and usually grouped with other payments. Both steps are defined in scheme rules such as the Visa Core Rules and the Mastercard Transaction Processing Rules.

The terms around them:

• Hold: the amount the issuer blocks on the cardholder’s account after approval. It lowers the available balance but is not yet a debit.
• Batch: a group of captured transactions sent by the merchant or PSP to the acquirer, usually once a day.
• Clearing: the exchange of final transaction details between acquirer and issuer through the scheme.
• Settlement: the movement of funds from the issuer to the acquirer, net of interchange. Our episode on settlement and payout covers what happens next.
• Funding: the payment from the acquirer, PSP or PayFac to the merchant’s bank account, often written T+N, where N is the number of business days after capture.
• Void: the cancellation of an authorization before capture, which releases the hold. See void transactions.

When both steps happen at once, the payment is called a sale or an auth-and-capture. This is common in shops and for digital goods. Separate steps are common online, for physical goods, rentals and hotels.

The channel also matters. In a shop, the card is read by a terminal and the authorization carries chip data; in e-commerce, the merchant relies on the card details and on authentication. Schemes therefore give different validity windows to card-present and card-not-present authorizations, and an operator that runs both channels has to manage two sets of deadlines for the same merchant.

Final, pre-authorization, incremental: which authorization types exist?

Schemes distinguish authorizations by how certain the final amount is. The type chosen changes how long the hold can last.

• Final authorization: the amount is known and will not change. It must be captured quickly and for the same amount.
• Pre-authorization or estimated authorization: the amount is an estimate, as for a hotel stay, a car or a bike rental. It can last longer and be adjusted.
• Incremental authorization: an extra approval added to an existing one when the final amount grows, such as an extra night.
• Partial capture: the merchant captures less than authorized, for example when only part of an order ships. The rest must be released or captured later within the time limit.
• Account verification: a zero-amount check that the card is valid, used before storing a card on file. No hold is placed.
• Force-post: a transaction captured without a valid authorization, or after the authorization has expired. It is the exception the rules try to prevent.

How does authorization and capture work?

The full path runs from the checkout to the merchant’s bank account. Here is the sequence for an online order shipped two days after purchase:

1. Authorization request: the shopper pays 80.00. The PSP sends the request through the acquirer and the scheme to the issuer, identified by the card’s BIN.
2. Approval and hold: the issuer checks the card, the risk and the available funds, approves, and blocks 80.00.
3. Order processing: the merchant prepares the parcel. Nothing has been charged yet.
4. Capture: on shipment, the merchant captures 80.00, or 60.00 if one item is out of stock, and releases the rest.
5. Batch and clearing: at the daily cut-off, the PSP sends the captured transactions to the acquirer, which submits them to the scheme for clearing.
6. Settlement: the issuer pays the acquirer the cleared amount minus interchange, typically within one or two business days.
7. Funding: the acquirer, PSP or PayFac pays the merchant according to its contract, net or gross of fees, after any reserve.

In a restaurant, the same logic applies with a twist: the terminal authorizes the bill, and the tip is added before the batch closes, so the captured amount is higher than the authorized one within limits set by the schemes. In a hotel, the sequence can last a week, with an estimated authorization at check-in, incremental authorizations during the stay and a capture at check-out.

Authorization and capture in numbers (2026)

Scheme rules put precise limits on how long a hold can wait for its capture.

• 5 and 10 days: since April 13, 2024, a Visa authorization is valid for five calendar days for most card-present and merchant-initiated transactions and ten days for cardholder-initiated card-not-present ones, according to Visa’s updated authorization framework.
• 30 days: the validity of a Visa estimated authorization for lodging, cruise lines and vehicle rental, under the same framework. Later captures can be disputed for late presentment.
• 7 and 30 days: the usual Mastercard clearing windows for final authorizations and pre-authorizations, as described in Revolut’s developer documentation.
• USD 0.05: the Visa Europe fee per authorization that is neither captured nor reversed in time, since July 2024, under the processing integrity program described by Solidgate.
• Exact amount: in the EU, PSD2 (Directive (EU) 2015/2366), Article 75, allows funds to be blocked on a card only if the payer agreed to the exact amount, and requires the release of the block without undue delay once the amount is known.

What are the risks and limits of separating authorization and capture?

A delayed capture gives flexibility, but every day between the two steps carries a cost or a risk.

• Expired authorizations: a capture after the validity window can be declined, charged a fee or disputed by the issuer as not authorized.
• Force-post exposure: capturing without valid authorization leaves the merchant without protection if the cardholder disputes the payment.
• Open holds: unused holds lock the cardholder’s funds, generate complaints and, in Europe, scheme fees.
• Amount mismatch: capturing more than authorized usually needs an incremental authorization; capturing less needs a release of the rest.
• Batch failures: a missed cut-off delays settlement and funding by a day, and a lost batch means unpaid sales.
• Customer confusion: a shopper who sees both a hold and a final charge, or a hold that has not disappeared yet, may contact the bank and open a dispute.
• Cash-flow lag: funding at T+2 or later, plus reserves, leaves merchants waiting for money they have already earned.

Authorization and capture: what changes for PSPs, PayFacs and platforms

For an operator, the two steps are configuration choices that must match each merchant’s business. Five areas matter most.

Capture strategy per merchant

Digital goods and in-store sales can use immediate capture. Physical goods should capture at shipment. Rentals, hotels and services billed after use need estimated and incremental authorizations. An operator should set the capture mode per merchant or per MCC, not once for the whole platform, and send the right authorization indicator so that issuers apply the right validity window.

Expiry and reversal management

Holds that will not be captured should be released, not left to expire. Automated reversals at cancellation, and captures scheduled before the scheme deadline, avoid integrity fees and late-presentment disputes. A declined capture is also a signal: some declines can be retried, as explained in soft declines, while others mean the payment is lost.

Routing and multi-acquiring

A transaction must be captured with the acquirer that authorized it. This sounds obvious, but it becomes a design constraint as soon as a platform sends traffic to two or three acquirers, retries declined payments elsewhere or migrates merchants between providers. Operators that route authorizations across several acquirers need to keep the link between each authorization and its acquirer, and to capture and refund through the same path.

Reconciliation

Authorized, captured, cleared, settled and funded amounts rarely match one to one: partial captures, fees, refunds and reserves sit in between. Matching every capture to its settlement line and to the bank credit is the core of payment operations. In NORBr, reconciliation and settlement data from the connected providers is gathered on one platform, and consolidated reporting and reconciliation gives one view across them. The approach is detailed in streamlining financial reconciliation, and the in-store case in how matching simplifies POS transaction reconciliation.

Disputes

The authorization record is the merchant’s first piece of evidence. When a cardholder disputes a payment, the issuer checks whether a valid authorization existed for the captured amount and date. Captures made late, for a higher amount without an incremental authorization, or without any approval, are among the easiest chargebacks for an issuer to win. Keeping authorization codes, timestamps and amounts linked to each capture makes these disputes simple to answer.

Funding and payouts

Merchants judge a provider by when the money lands. A PayFac sets its own funding schedule, net or gross, and must show each merchant how captures turn into payouts after fees and reserves. In the United States, where batches, debit networks and next-day funding are part of daily operations, the guide to payment methods in the United States gives the local context.

For the structure of the acquiring market behind these steps, the Payments Library lists Merchant Acquiring Industry Dynamics. The #TheShot episode Payments are just the start looks at what operators build once the money flows reliably.

Should authorization and capture be separated in 2026?

Yes, whenever the final amount or the delivery date is not certain at checkout. Separation protects shoppers, who are not charged for goods that never ship, and merchants, who can adjust the amount without a refund. The price is discipline: every hold needs an owner and a deadline. What it means by player:

• PSPs: offer delayed, partial and incremental capture, with deadlines enforced automatically by card scheme and authorization type.
• PayFacs: configure capture rules per sub-merchant and explain funding timelines clearly, because payout delays drive support tickets.
• ISOs: check that the acquirer and terminal setup support the capture modes their merchants need, such as tips or pre-authorizations.
• ISVs and platforms: capture at the business event, such as shipment, check-out or job completion, and release what will not be charged.

Authorization reserves the money and capture collects it, and operators who manage the time between the two avoid fees and disputes while paying their merchants on time.