Improving Authorisation Rates

Measure it properly first

Authorisation rate is often quoted as one number, which hides the useful detail. Break it down by issuer country, card brand, currency, transaction type and whether the payment was a first charge or a renewal.

The pattern that emerges usually points at one or two specific problems rather than a general malaise.

Hard versus soft declines

A hard decline — stolen card, closed account, invalid number — should never be retried. A soft decline is a temporary condition, and a well-timed retry frequently succeeds.

Retrying hard declines is not just wasted effort; excessive retries can trigger issuer-level blocking. Read the response codes your gateway returns and branch on them rather than retrying uniformly.

Send better data

Issuers approve transactions they can verify. Incomplete or inconsistent data at authorisation lowers approval rates in ways that are easy to fix.

• Full billing address and postal code where the acquirer supports verification
• Card security code on first, non-recurring transactions
• Correct transaction indicators for recurring, instalment and card-on-file charges
• A stored-credential framework applied consistently across the customer lifecycle
• Consistent merchant category and descriptor data
• Authentication data where it is available and applicable

Currency and geography

Cross-border transactions are approved at lower rates than domestic ones. Presenting prices in the customer’s currency and, where volume justifies it, processing through an acquirer local to that market can improve both approval rates and customer trust.

Local payment methods matter too. In several markets a bank-transfer or wallet method converts better than cards, and adding one can lift overall completion more than optimising card authorisation.

Checkout mechanics

Some of the biggest gains are not payment-network issues at all. Card-number formatting, inline validation, wallet support, remembering returning customers, and a clear message when a card is declined all affect completed payments.

A generic “payment failed” message loses customers who would have used a second card. Tell them what happened, in language they can act on.

Routing and redundancy

For eligible merchants running more than one account, routing lets you send traffic to whichever provider performs best for a given segment, and to fail over when one has an outage.

It adds reconciliation complexity, so it is worth doing deliberately rather than by default. Eligibility for a second account is always determined by each provider’s underwriting.