Authorization rate is the percentage of payment authorization requests that are approved by an issuer, bank, or payment provider.
In card payments, authorization happens when the customer’s issuing bank checks whether a transaction should be approved or declined. The issuer may consider available funds, card status, authentication results, fraud signals, transaction data, and risk rules before making a decision.
Authorization rate shows how many attempted payments receive an approval response.
Authorization rate is usually calculated by dividing the number of approved authorization requests by the total number of submitted authorization requests. For example, if a business sends 1,000 authorization requests and 850 are approved, the authorization rate is 85%.
The exact calculation may vary depending on how a business defines payment attempts, retries, duplicate attempts, soft declines, and technical failures.
Authorization rate and payment acceptance rate are closely related, but they are not always the same. Authorization rate usually focuses on issuer or provider approval and measures how many transactions are authorised after being submitted for approval. Acceptance rate, in its turn, can be broader. It may include more stages of the payment flow, such as checkout completion, fraud screening, authentication, technical processing, and final payment success.
In simple terms, authorization rate measures approval at the authorization stage. Acceptance rate can reflect the overall ability to convert payment attempts into successful payments.
Authorization rate is an important payment performance metric because every declined payment can mean lost revenue, customer frustration, or extra operational work.
A low authorization rate may point to issues such as:
For merchants, PSPs, and payment teams, tracking authorization rate helps identify where payments fail and which providers, markets, cards, or transaction types need attention.
Authorization rate is often monitored alongside payment conversion rate, acceptance rate, decline rate, chargeback rate, and provider performance. For businesses working with multiple PSPs, acquirers, currencies, and markets, authorization rate can vary significantly by route. This makes it important to analyse authorization data by provider, country, payment method, card type, issuer, and transaction segment.
A central payment infrastructure layer can help payment teams compare routes, monitor approval performance, and adjust routing logic based on transaction data.
At Corefy, authorisation rate is treated as part of broader payment performance management. Teams can monitor approval and decline patterns across providers, markets, payment methods, currencies, and transaction routes, then use this data to adjust routing, cascading, and provider logic. This helps understand where payment failures occur and manage authorisation performance with more control.
