Authorization Hold
Pronunciation: aw-thur-uh-ZAY-shun HOHLD
Definition
An authorization hold temporarily reserves part of a payer's available balance before a card transaction is completed, adjusted, or released. An authorization hold is a temporary reservation placed after a card issuer approves an authorization request. It reduces the cardholder's available spending capacity without immediately creating the final posted transaction or transferring settled funds to the merchant. The final captured amount may equal, reduce, or sometimes adjust the original authorized amount according to network and merchant rules.
Overview
An authorization hold is a temporary reservation placed after a card issuer approves an authorization request. It reduces the cardholder’s available spending capacity without immediately creating the final posted transaction or transferring settled funds to the merchant.
The final captured amount may equal, reduce, or sometimes adjust the original authorized amount according to network and merchant rules. If the merchant does not capture the transaction, the hold should expire or be released, though timing varies by issuer and transaction type.
Merchants should use accurate amounts, capture promptly, reverse unused authorizations, and explain visible pending charges. Poor hold management can tie up customer funds, increase support contacts, create duplicate-looking entries, and reduce authorization performance.
For Authorization Hold, production scope should name the relevant customers, merchants, orders, credentials, payment instructions, balances, refunds, and settlement obligations, the decision being supported, the accountable owner, and the time and jurisdiction boundaries.
An authorization hold temporarily reserves part of a payer’s available balance before a card transaction is completed, adjusted, or released. An authorization hold reserves spending capacity temporarily; it is not final settlement and should be captured, adjusted, or released correctly.
For Authorization Hold, the trust decision should establish authorization hold temporarily reserves part of a payer’s available balance before a card transaction is completed, adjusted, or released and bind the result to the requested action and protected resource. Teams should test issuance, storage, validation, expiry, revocation, recovery, and privileged override for permissions and protected actions, rather than checking only a successful request. Logs concerning the Authorization Hold context and permissions and protected actions should support investigation without exposing reusable secrets or unnecessary personal data.
Key Takeaway
An authorization hold reserves spending capacity temporarily; it is not final settlement and should be captured, adjusted, or released correctly.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)
- FATF Documentation: Virtual Assets — FATF (2026-07-30)