This term
What it means
The authorised amount is the number at the heart of every card approval. When the issuing bank says yes, it says yes to a figure: this merchant may claim up to this amount.
That reservation immediately reduces the cardholder's available balance or credit, even though no money has moved. The amount is chosen by the merchant at the moment of authorisation, and it is often an estimate.
Restaurants authorise the bill before the tip, fuel pumps authorise a ceiling before the tank is filled, and hotels authorise the stay plus a buffer for incidentals. The final settled amount then matches or undercuts the reservation, and card network rules allow adjustments such as tips and tolerances for certain merchant types, so the posted charge can exceed the authorised amount modestly without a new approval.
Beyond those tolerances, the merchant needs incremental authorisation. The reservation is real money from the cardholder's perspective, so a $500 hold on a $600 available balance leaves $100 of spending power, and additional purchases decline even though the account holds more than enough cash.
The Consumer Financial Protection Bureau's consumer guidance is a useful reference on how pending holds differ from charges that were never authorised. For issuers, the authorised amount is a control lever.
Approvals are capped by available credit, account balance, fraud scoring, and merchant category, so the amount itself is a decision, not a formality, and partial authorisations, approving less than requested, let a sale go through with split payment. Merchants manage the amount strategically too: authorising too little invites declines at completion, while authorising far too much ties up customer funds and invites complaints and regulatory attention, so best practice is to authorise close to the expected final figure and adjust incrementally.
For non-finance managers, the term matters in cash planning and customer service. A customer asking why their card was declined after a purchase is usually asking about an authorised amount sitting as a hold, and support teams that can read pending authorisations resolve these calls in one touch.
Disputes sometimes hinge on the figure as well: a cardholder who approved $80 and was charged $110 without a tip or tolerance justification has grounds for a chargeback, and the merchant's authorisation record is the evidence both sides examine. Processors surface the figure in every authorisation response, and smart payment stacks log it for reconciliation, so discrepancies between authorised and captured amounts are a standard audit trail in payment reviews.
Tokenisation has not changed the logic, since a device token standing in for the card number still draws its approval against the same underlying amount and reservation rules. As payments go instant and account-based, the same concept reappears as reserved balances and pre-approvals in newer rails, with the authorised amount still marking how much of the customer's money is spoken for.
In practice
Real-world examples
Example 1
A pump authorises a $100 ceiling, then settles the actual $38 dispensed, releasing $62. The customer sees the full $100 hold for a day or two and then the final $38 charge. The released $62 returns to available funds as soon as the issuer processes the completion.
Example 2
An issuer partially authorises $300 of a $450 request, and the customer pays the remainder in cash. The terminal prints the approved amount and asks for the balance of $150. The sale completes without a second card.
Example 3
A cardholder disputes a $140 charge after approving $95, and the merchant's records show no tolerance justification. The issuer reviews the authorisation record and the receipt, which confirm the $95 approval. The cardholder receives a credit for the $45 difference.
Formula
Available credit after approval = credit limit - posted balances - sum of pending authorised amounts
Example
A $2,000 limit with $1,100 posted and a $250 authorisation leaves:
$2,000 - $1,100 - $250 = $650
Available until the $250 settles or expires.
Now add a tip.
A restaurant authorises $64 and the diner adds a $12 tip, so the charge settles at $76.
The tip is:
12 / 64 = 18.75%
Above the authorised amount, which is the kind of variance that network tolerances for restaurants are designed to absorb without a new approval.
Case study
Seen in the real world
This is a fictional example. Lumen Bistro, an invented restaurant, authorises $64 for a dinner; the cardholder adds a $12 tip, and the charge settles at $76 within network tolerance. On the same card, $900 of available credit drops to $836 when the $64 is authorised, and to $824 while the $76 charge is pending. The cardholder's later $850 purchase declines, even though no money has left the account, and the support call explains the pending reservations. Once the dinner posts and the bank updates the balance, the cardholder tries the purchase again and it is approved.
Watch out
Common mistakes
- Treating the authorised amount as a charged amount in revenue reports, when settlement is the event that moves money. Pending approvals are not sales until they post.
- Authorising generous round numbers as a habit, which strands customer funds and triggers declines on their other purchases. Estimate realistically and release promptly.
- Ignoring adjustment tolerances when reconciling, so legitimate tip and buffer variances get flagged as errors. Match charges with tolerance rules in mind.
Questions
People also ask
Who sets the authorised amount?
The merchant requests it, and the issuer approves, partially approves, or declines based on available funds, credit, and risk checks.
Can the final charge exceed the authorised amount?
Yes, within network tolerances for categories like restaurants and hotels, typically for tips or incidentals; larger excesses need additional authorisation.
When does the reservation release?
When the transaction settles, when the merchant reverses it, or when the hold expires under network time limits.