Authorisation Hold
An authorisation hold is the amount an issuer reserves against a cardholder's available balance or credit limit when it approves an authorisation — visible as "pending" — until the merchant captures, voids, or the hold expires under the issuer's and schemes' timing rules. It is why a hotel's deposit reduces the balance at check-in and why "the merchant hasn't charged me but the money is gone" is a support call.
- Also known as
- Pre-authorisation, Card hold, Pending charge
- Used at
- every authorisation — the hold is the issuer's side of the approval; conspicuous where authorisation and capture are far apart or the amounts differ: hotels, car rental, fuel, deposits, marketplaces, subscription trials
- Binding
- the schemes' rules on authorisation validity (7 days standard, 30 for hotels and rentals, with re-authorisation for longer); the issuer's own release timing on expired or reversed holds — often longer than the merchant's void, which is the customer-service gap
- Typical duration
- a captured authorisation converts to a charge within days; a voided one is released when the issuer processes the reversal (hours to several days); an uncaptured one expires on the issuer's timetable, sometimes up to 30 days on debit cards
- Typical misuse
- authorisations for estimates far above the final amount (a fuel pump's €150 hold for a €40 fill), held for days on a debit card; the schemes and regulators have pushed real-time partial reversals (fuel dispensers now send the final amount within minutes) to fix it
- Parties
- the issuer (which holds), the merchant (which caused it), the acquirer and network (which carry the void or capture), and the cardholder whose available balance is reduced
How an authorisation hold works in practice
A guest checks into a hotel; the desk authorises €500. The issuer approves and places a €500 hold; the guest's available balance falls by €500 though no charge has posted. At check-out the hotel captures €380 for the bill; the issuer converts €380 of the hold into a charge and should release the remaining €120 — and does, on its own schedule, which may be the next day or the next week. If the hotel captured without a partial reversal for the difference, the €120 hold sits until it expires. The guest, seeing €500 pending and a €380 charge, calls someone; the hotel's answer ("that's your bank") and the bank's ("that's the merchant") are both a quarter true.
The mechanics that reduce the pain: merchants void or reverse the unused portion at capture (a partial reversal message the schemes support and many merchants never send); fuel dispensers send a completion advice with the real amount within minutes; marketplaces and e-commerce sites authorise for the order amount rather than an estimate; and issuers release holds on reversal quickly. The schemes' rules on authorisation validity bound the worst cases, and their misuse fees penalise merchants that authorise without capturing.
For a fintech issuer, hold management is a product decision — how fast the app shows a released hold — and a support-cost line; for a merchant, it is the difference between a customer who understands the pending charge and one who disputes it.
Example
A car-rental company authorises €800 at pickup on a debit card, captures €420 at return, and sends no partial reversal. The customer's bank keeps the €380 hold for eleven days — its policy on debit authorisations — and the customer, unable to pay rent, disputes the €800 as "charged twice". The rental company's payments team implements partial reversals at return and re-authorisation at day six for long rentals; their acquirer confirms the reversal reaches issuers within hours. Support tickets about holds fall by 70% over a quarter; the chargebacks for "duplicate charge" — which the company had been losing because the cardholder's statement showed €800 pending — stop. The team's next request to the issuers, through the scheme, is that debit holds be released in a day; the scheme's rule change follows two years later.
Common mistakes
- Authorising an estimate far above the final amount, especially on debit cards. - Capturing less than the authorisation without a partial reversal for the rest. - Voiding through the merchant's system and assuming the issuer releases the hold the same hour. - Support scripts that blame the bank for a hold the merchant caused, or the reverse. - Issuers whose apps show a released hold days after it was reversed.