Authorized transaction

What is an authorized transaction?

Authorized transaction is a debit or credit card purchase that the cardholder's

has approved, confirming that the account holds enough funds and that the card is valid to complete the payment. Approval doesn't move any money yet; it reserves the amount and returns an authorization code that lets the merchant proceed.

Authorization is the first half of a two-step card flow. Several parties take part: the

cardholder

, the merchant, the

acquirer

that processes payments on the merchant's behalf, the card network, and the issuer that holds the cardholder's account. Once the issuer approves, the transaction is authorized but not yet settled – settlement happens later at

capture

Key facts

Also known as: purchase authorization, payment authorization
Applies to: card-present and
card-not-present
card payments
Outcome: either an approval that returns an
authorization
code, or a
decline
with a reason code
Effect on funds: the approved amount is held on the cardholder's account, not transferred – the money moves only at capture
Hold duration: an authorization hold lasts a limited time and lapses if the merchant doesn't capture it, though the exact window varies by card network and acquirer
Next step: the merchant captures the authorization to collect the funds, or voids it to release the hold

How authorization works

Initiation. The cardholder presents a card at checkout – swiped, tapped, or entered online – and the amount is submitted for approval.
Routing to the acquirer. The merchant's
payment processor
or acquirer receives the request and forwards it to the relevant card network.
Network routing. The card network passes the authorization request to the issuer that holds the cardholder's account.
Issuer decision. The issuer checks the available balance, the card's validity, and fraud signals such as
address verification
, then returns an approval or a decline.
Authorization response. On approval, the issuer returns an authorization code and places a hold on the funds. On refusal, it returns a
decline code
explaining why.
Capture or void. The merchant
captures
the authorization to settle the payment, or issues a
void
to cancel it before capture and release the hold.

Why it matters

Authorization confirms that a card is valid and backed by funds before the merchant releases goods or services, which stops fulfilment against an expired card or an empty account. It also splits approval from settlement, so a merchant can authorize at checkout and capture once an order ships. Until the merchant captures or the hold expires, the reserved amount shows on the cardholder's account as a pending charge that lowers their available balance without being debited.

An issuer weighs each request against its own risk signals, so identical orders can be approved for one cardholder and declined for another. The size of the hold can also be corrected after approval through an

authorization adjustment

when the final amount differs from the amount first authorized – for example, when a tip or a shipping charge is added.

Common issues

Declines. Insufficient funds, an expired card, or a suspected-fraud flag return a
decline code
instead of an approval.
Expired holds. An authorization hold lapses after a set period. If it expires before the merchant captures, the merchant needs a
force capture
or a fresh authorization to collect the funds.
Amount mismatches. When the captured amount differs from the authorized amount, an
authorization adjustment
aligns the hold with the final total.