How to improve your payment approval rate

What is a payment approval rate?

Small changes in approval rate can matter a lot to revenue, because every declined payment from a real customer is a sale you already paid to acquire. Treat approval rate as something to manage continuously, not a number to check once a quarter.

A payment approval rate is the percentage of payment attempts that are approved, out of all attempts sent for approval. It's one of the clearest signals of how healthy your payment setup is.

Approval rate, authorization rate and checkout conversion get mixed up. Define which one you're tracking and stick to it. Comparing your approval rate with someone else's authorization rate doesn't tell you much.

• Authorization rate usually means card authorizations approved by the issuer, out of authorizations sent.
• Approval rate is often used more broadly and can include non-card methods and declines from your own fraud rules or provider rules.
• Checkout conversion measures how many shoppers who start checkout end up paying, so it includes people who abandon before submitting payment.

How do you calculate approval rate?

Approval rate = approved payment attempts divided by total payment attempts, times 100.

Decide upfront how to count retries. If a customer tries three times and the third attempt succeeds, is that one success out of three attempts, or one successful payment out of one intent? Many teams track both: attempt-level approval rate (for provider and routing analysis) and intent-level approval rate (for business impact).

Why do payments get declined?

Declines come from different places, and each needs a different fix.

Issuer declines. The cardholder's bank declines the transaction. Common reasons include insufficient funds, suspected fraud, card restrictions (for example, cross-border or online use disabled), expired cards, or incorrect card details.

Soft declines vs hard declines. A soft decline is temporary. The payment might succeed later, with another route, or after authentication. Examples include issuer unavailable, a timeout, or a request for strong customer authentication. A hard decline is final for that card and transaction. Examples include a closed account, a lost or stolen card, or an invalid card number. Retrying a hard decline won't help, and repeated retries can conflict with card scheme rules, which limit retries of declined transactions.

Technical and provider errors. Some failures never reach the issuer. They include timeouts, connection errors, provider outages, malformed requests or configuration problems. These are often the easiest declines to recover, because a second provider or a short retry can solve them.

Authentication and fraud-related declines. Payments can fail because 3-D Secure wasn't completed, or because a fraud rule (yours or the provider's) blocked them. Some of these are correct decisions. Others are false positives that block real customers.

How do you measure approval rates properly?

One overall number hides the problem. Break approval rate down by the segments below.

Normalizing decline reasons matters most. Each provider returns codes in its own format. Without one common model (soft vs hard, issuer vs technical vs risk), you can't compare providers or decide what's safe to retry.

• provider and route
• country of the card vs country of the merchant
• card type, card brand and payment method
• transaction type: first payment, recurring, merchant-initiated
• amount band
• decline reason, normalized across providers
• device and checkout flow

How can you improve approval rates?

Send complete, clean transaction data. Issuers decide with the data you send them. Include accurate billing details, the cardholder name, a correct transaction type, a clear statement descriptor and, where supported, extra data that helps issuers and authentication flows assess risk (the exact fields depend on your provider and the 3-D Secure version). Validate card numbers and expiry dates in checkout so obviously bad attempts never get sent.

Route transactions to the right provider. Not every provider performs the same for every card, country or currency. Routing by card country, currency, payment method or provider health can help each transaction reach a route that's more likely to approve it. Start with simple rules based on your own data, then refine them. See our guide to payment orchestration.

Cascade soft declines, never hard ones. When a payment fails with a soft decline or a technical error, sending it again through another provider can recover the sale. That's payment cascading. Keep it strict: cascade only on declines you've marked as retryable, set a maximum number of attempts, use idempotency keys to avoid double charges, and don't cascade hard declines or clear fraud signals.

Keep stored cards up to date. For subscriptions and saved cards, declines often come from expired or replaced cards. Network tokens and card updater services can keep stored credentials current, where your providers support them; availability varies by provider.

Balance strong authentication and friction. In regions with strong customer authentication rules, a missing authentication can cause declines, but adding friction to every payment can increase abandonment. Use exemptions where they're allowed and appropriate, and make sure authentication results are passed correctly to the provider. For details, see our 3-D Secure 2 guide.

Tune fraud rules instead of tightening them blindly. Very strict rules block fraud, and they also block good customers. Review what your rules decline, look for false positives, and use transaction risk scoring so low-risk payments go through smoothly and only the risky ones get extra checks or a decline.

Retry recurring payments at the right moment. For merchant-initiated recurring payments, timing matters. Spread retries over days instead of minutes, avoid retrying hard declines, and tell the customer before access is cut off.

What should you do about each decline type?

Each decline type needs a different response. Use this as a starting point for your retry and cascading rules.

Which mistakes hurt approval rates?

These are the patterns that most often drag approval rates down.

• Retrying every decline automatically, including hard ones.
• Looking only at the overall approval rate instead of segments.
• Comparing providers without normalized decline codes.
• Letting fraud rules grow over time without reviewing false positives.
• Ignoring technical failures because they aren't real declines. They are lost payments too.

How does OrsunPay help?

OrsunPay is a payment orchestration platform that connects you to licensed PSPs; it does not process or hold funds itself. You connect your own PSP accounts through one integration, and smart routing and retries on retryable declines are live, with one view of approvals and declines across providers. The RiskCogs anti-fraud module adds a risk score and signals to each transaction, so checks can be applied where they're needed. Talk to us to review where your declines come from.