What Is Authorization? Definition, Payment Flow, and Examples
Authorization is the issuer-side decision on whether to approve a transaction based on account, amount, and risk data; it does not mean final merchant payment. This guide focuses on Authorization's real role, boundaries, and common points of confusion.
Key points
- Definition: Authorization is the issuer-side decision on whether to approve a transaction based on account, amount, and risk data; it does not mean final merchant payment.
- Flow position: The merchant sends an authorization request, and the issuer side returns an approval or decline based on account, amount, credentials, risk, and product rules.
- Do not confuse: Authorization / Capture
How it fits into the payment flow
For Authorization, the relevant process is as follows: The merchant sends an authorization request, and the issuer side returns an approval or decline based on account, amount, credentials, risk, and product rules. Authorization codes, response data, and decline codes describe that decision; they are not capture, posting, or final merchant funding.
A practical review of Authorization should account for this: A merchant should handle declines according to response information and network rules without exposing sensitive internal detail. A soft decline may support an appropriate authentication or retry path, while repeated submission is not a sound answer to a hard decline.
Practical example
After a store submits authorization, the issuer approves and the account shows a pending amount. The transaction moves toward formal posting only if the merchant later captures and clearing follows.
How it differs from related terms
| Term | Definition |
|---|---|
| Authorization | is the issuer-side decision on whether to approve a transaction based on account, amount, and risk data; it does not mean final merchant payment |
| Capture | is the merchant's confirmation after authorization that submits the transaction toward clearing; it is not completed interparty settlement |
| Settlement | is the actual movement of funds between relevant participants based on clearing results, while merchant payout timing depends on agreements |
Authorization focuses on the fact that it is the issuer-side decision on whether to approve a transaction based on account, amount, and risk data; it does not mean final merchant payment. Capture, by contrast, is the merchant's confirmation after authorization that submits the transaction toward clearing; it is not completed interparty settlement. They can appear in one transaction while answering different questions.
Use cases and limits
A key limit of Authorization is the following: blind retries can create duplicate holds, trigger controls, or worsen the customer experience. Approval is only a prerequisite for later processing; fulfillment and final accounting remain separate.
Frequently asked questions
These answers address two common search questions about Authorization.
Is it the same as Capture?
No. Authorization is the issuer-side decision on whether to approve a transaction based on account, amount, and risk data; it does not mean final merchant payment. Capture is the merchant's confirmation after authorization that submits the transaction toward clearing; it is not completed interparty settlement. Compare the object, processing stage, and responsible party.
Does an authorization code mean the merchant has received funds?
For Authorization, no. It relates to the authorization decision. Posting and interparty settlement generally follow capture, clearing, and settlement steps.
These primary sources support the definition and process for Authorization. Current product, network, and local rules still control a real transaction.