Card authorization
Card authorization is the real-time request and response process by which a merchant's payment system requests approval from the cardholder's issuing bank to proceed with a transaction, with the issuer approving or declining based on available balance, fraud scoring, and program-specific spend controls.
Card authorization happens in milliseconds. When a cardholder taps or inserts a card, the terminal sends an authorization request through the acquiring bank and card network to the issuing bank. The issuer evaluates the request against available balance, fraud rules, spend controls, and compliance checks, then returns an approval or decline code. The entire process typically completes in 2–3 seconds.
For card issuers managing their own programs, authorization logic is a core product capability. Spend controls, such as merchant category locks, amount limits, geographic restrictions, and day/time rules, are enforced within the authorization decision. A corporate card locked to business travel merchants declines at a supermarket because the MCC fails the program's spend policy rules, regardless of available funds.
Authorization rates, the percentage of transactions receiving approval, are a critical performance metric. Low authorization rates indicate over-aggressive fraud scoring, incorrect spend controls, or technical issues. High decline rates frustrate cardholders and reduce card utility.
Authorization quality defines the cardholder experience. A card that declines legitimate transactions loses user trust quickly. A card with insufficient fraud controls generates chargeback losses. The authorization layer is where issuer economics, cardholder experience, and fraud risk management intersect.
- Real-time authorization decisioning must complete in sub-second timeframes
- Fraud scoring models must balance false positive rates against false negatives
- Spend control logic must handle edge cases without excessive legitimate declines
- Cross-border authorization requires routing through international card network infrastructure
- Authorization system availability must meet card network uptime requirements, typically 99.99% or higher
A fintech launching a multi-currency corporate card through Nium configures authorization rules at corporate group, department, and individual cardholder levels. Travel department cards approve for airlines, hotels, and car hire; finance team cards approve for software subscriptions and professional services only. The layered authorization logic reduces expense policy exceptions by 94% in the first quarter.
Related Concepts
Nium's card issuing platform gives program managers full control over authorization logic, letting them configure spend controls, fraud rules, and approval criteria at the program, group, and individual card level. Nium's authorization infrastructure processes approvals and declines in real time, with webhook notifications for every authorization event.
Answers you didn't know you needed.
What is an authorization hold?
An authorization hold, or pre-authorization, reserves funds in the cardholder's account for a transaction that has been approved but not yet finalized. Hotels and car rental companies commonly place authorization holds. The hold is released and replaced by the final settlement amount.
What causes a card authorization decline?
Common decline reasons include insufficient balance, a card reported lost or stolen, a transaction failing spend control rules, fraud scoring flagging the transaction, or technical issues in the authorization chain.
What is the difference between authorization and settlement?
Authorization approves and reserves funds. Settlement is the actual transfer of funds from the cardholder's issuer to the merchant's acquirer, typically occurring in a batch process after the merchant captures the authorized transaction.
How quickly does card authorization happen?
Authorization typically completes in 2–3 seconds in modern card infrastructure. API-native issuers like Nium process authorizations in sub-second response times.
Can card authorization be customized for different card programs?
Yes. Nium's authorization infrastructure supports fully customizable program logic: different spend rules, fraud controls, and authorization criteria can be configured per program, cardholder group, or individual card.