What it means
When a customer pays by card, the terminal or checkout page sends an authorization request through the merchant's acquirer to the card network and on to the issuing bank. If the issuer approves, it returns a response containing a code, usually around six alphanumeric characters, and places a hold on the cardholder's available balance.
The distinction that trips people up is between authorization and settlement. Authorization only reserves funds and creates a promise, while the cash reaches the merchant's account once the transaction is captured and settled, often a day or more later.
Until then the sale sits as an unsettled balance rather than as cleared money. Finance and operations teams care about the code because it is the thread that ties everything together.
Every deposit from the acquirer can be traced back through the code to the original order, which is how mismatches between the sales ledger and the bank statement get resolved. Authorization codes also matter in chargeback defence.
If a cardholder disputes a payment, the merchant's evidence pack normally includes the code, the approval timestamp and the address verification result, which together show that the issuer itself approved the transaction at the time. Two variants are worth knowing.
A pre-authorization reserves an estimated amount, common in hotels and at fuel pumps, and is adjusted to the true figure later; separately, an authorization expires, often within about a week, after which the hold falls away and the merchant has to request approval again.
In practice
Real-world examples.
Example
A hotel takes a $400 pre-authorization at check-in against an expected $310 bill. At checkout the property captures only the actual $310, and the difference drops off the guest's available balance a few days later once the original hold expires.
Example
A subscription business sees a spike in failed renewals and pulls the response codes behind the failures. Most are soft declines caused by expired cards, so it switches on an account updater service and recovers a large share of the affected accounts within one billing cycle.
Example
A retailer's finance team cannot match a $6,480 acquirer deposit to its sales ledger. Using the authorization codes on the settlement file, it identifies two transactions authorized on the last day of the month but captured on the first day of the next, and posts them to the correct period.
Formula
Calculation
Authorization approval rate = (Approved authorizations / Total authorization requests) x 100
An online retailer processes 48,000 card authorization requests in a month and 45,120 of them are approved. The approval rate is 45,120 / 48,000 = 0.94, or 94.0%, leaving 2,880 declined attempts.
At an average order value of $85, those declines represent 2,880 x $85 = $244,800 of gross order value that did not convert. Suppose the payments team estimates that half of the declines are recoverable through smarter retry timing and updated card credentials: that is 1,440 orders worth 1,440 x $85 = $122,400.
Framed as a target, lifting the approval rate from 94.0% to 96.0% would produce 48,000 x 0.96 = 46,080 approvals, which is 960 more than 45,120. At $85 each that is 960 x $85 = $81,600 of additional monthly revenue from no extra marketing spend at all.Case study
Seen in the real world.
Harbour Lane Supplies is a fictional online trade supplier used here purely as an illustrative example. Its finance manager noticed that revenue reported by the checkout system was consistently around 4% higher than the cash landing in the bank, and nobody could explain the gap.
Working through a month of data, the team found three separate causes hiding behind the same symptom. Some orders had been authorized but never captured because a warehouse step failed silently, some pre-authorizations on backordered items had expired before dispatch and needed a fresh approval that was never requested, and a handful of transactions had been captured for less than the authorized amount after items were cancelled.
The fix was procedural rather than technical: capture at dispatch, alert on any authorization older than five days, and reconcile daily using the authorization code as the matching key. The unexplained gap fell to under 0.3%, and the company recovered roughly $19,000 of orders that had been approved by issuers but never actually billed.
Watch out
Common mistakes.
- Treating an authorization code as confirmation that the money has arrived, when it only confirms the issuer has approved and reserved the funds.
- Letting authorizations expire before capture on backordered or made-to-order goods, which turns an approved sale into a decline weeks later.
- Discarding authorization codes after a sale completes, then having no evidence when a chargeback arrives six months on.
Questions
People also ask.
How long does an authorization hold last?
It varies by card scheme and merchant category, but commonly around five to seven days for retail purchases and longer for travel and hospitality.
Is a decline always a lack of funds?
No, many declines are risk or verification related, including expired cards, address mismatches and issuer fraud rules, which is why response codes matter more than the headline decline.
Can the same authorization be used for a partial capture?
Usually yes, the merchant can capture less than the approved amount, but capturing more generally requires a new approval.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%