Decline Rate
The decline rate is the share of card payment attempts that are refused at authorisation — by the issuer, the network or the merchant's own fraud rules — measured against attempts. For an online merchant every declined legitimate transaction is lost revenue, and for a payments company the approval rate it achieves for its merchants is a product in itself.
- Also known as
- Authorisation decline rate, Approval rate, Auth rate
- Used at
- every authorisation; reported by acquirer, by issuer, by country and by card type
- Typical range
- 5–15% of e-commerce attempts declined in Europe; 2–4% for card-present; much higher for cross-border
- Split
- hard declines (lost or stolen card, closed account) and soft declines (insufficient funds, issuer timeouts, suspected fraud) — soft ones can be retried
- Levers
- smart routing, network tokens, retry logic, 3-D Secure exemptions, local acquiring
- In a valuation
- a payments company's approval rate against the market's is a measure of its technology, and of the volume a buyer can add
How a decline rate works in practice
A cardholder enters card details; the merchant's payment provider sends an authorisation request through the acquirer and the network to the issuer, which says yes or no in under a second. It says no more often than merchants assume — one attempt in ten on a European e-commerce site, one in four on some cross-border corridors — and most of those refusals are not fraud. The card has expired and been reissued, the issuer's risk model disliked a foreign acquirer, the transaction lacked a strong-authentication exemption, the issuer's system timed out. Each is a sale the customer wanted to make.
Reducing declines is what a payments company sells to a merchant beyond a price. Routing the transaction through a local acquirer in the cardholder's country lifts approval rates by several points; network tokens replace expired card numbers automatically; retrying a soft decline a day later recovers a share of subscriptions; applying the right 3-D Secure exemption avoids a challenge the issuer would otherwise fail. A provider that approves 93% of attempts where the merchant's previous provider approved 89% has added 4% to the merchant's revenue at no cost to the merchant, and that arithmetic wins accounts.
In an acquisition, decline data is diligence on the product. A payments company that reports approval rates above its market has technology worth paying for; one below it has merchants who will leave when a competitor shows them the numbers. And a buyer that owns local acquiring in markets the target does not can model a revenue uplift from routing alone.
Example
A subscription merchant processes 1.2m renewals a year at an average of €30, with a decline rate of 12%: 144,000 failed renewals, €4.3m of billing that did not happen. Its new payment provider adds network tokens, retries soft declines at issuer-friendly times and routes European cards to local acquirers; the decline rate falls to 7.5%. Recovered renewals: 54,000, worth €1.6m a year, on a provider fee 0.1 points higher than before. The merchant's finance team calls it the best pricing decision it made that year.
Common mistakes
- Reporting approval rate on transactions rather than on attempts, which hides the retries. - Treating all declines as fraud prevention, and cutting sales to protect against a risk that was not there. - Comparing rates across countries and card types without segmenting: a 7% blended rate can hide 25% on one corridor. - Retrying hard declines, which annoys issuers and can breach network rules. - Buying a payments company on its revenue without asking what it approves.