Authorization

Authorization is the gatekeeping exchange that decides whether a card payment is allowed to move forward. The merchant asks the issuer whether a specific amount can be charged to a specific account, and the issuer answers in real time. That answer, and the data attached to it, shapes everything that happens next in the payment.

The request travels a defined path: from the merchant's checkout or terminal, through the gateway and processor, across the card network, and finally to the issuer that owns the account. The issuer checks whether the account is valid and in good standing, whether funds or credit are available, and whether the transaction fits its risk profile. It then returns a decision the merchant can act on immediately.

A key point is that authorization and funding are not the same event. An approval usually reserves the requested amount as a hold, but the money does not actually move until the transaction is cleared and settled later. That separation is deliberate: it lets merchants confirm a payment is possible at the moment of sale while the network handles the accounting of funds through its own cycle.

Authorization is the first control point where a merchant can stop a bad transaction before it ever touches settlement. A clean approval flow protects revenue by confirming that an account is open, the amount is acceptable, and the issuer is willing to stand behind the payment at that moment.

It also carries risk in the other direction. Treating an approval as proof that a sale is final can leave merchants exposed to reversals, holds, and later disputes. Reading authorization responses accurately, and pairing them with fraud screening, keeps avoidable losses out of the pipeline.

When a customer pays, the merchant's system sends an authorization request through its gateway and processor to the card network and on to the issuer. The issuer evaluates the account status, available funds, and its own risk rules, then returns an approval or a decline along with response data.

An approval typically places a hold on the cardholder's funds for the requested amount. The transaction is only completed later through clearing and settlement, which is why authorization and funding are handled as separate steps in the payment flow.

An approved authorization confirms only that the issuer accepted the request at that point in time. It does not guarantee that the transaction will settle, and it does not prevent the cardholder or issuer from raising a dispute afterward. Authorization approval, settlement, and dispute rights are separate stages, and a payment can succeed at one stage while still being challenged at another.