A customer has already chosen the product, entered their details and clicked Pay.
If the transaction fails, the business loses a payment attempt from someone who was ready to buy.
Payment success rate (PSR) measures how many attempted payments complete successfully. But the useful question is not only, “What is my PSR?” It is “Where are the failed attempts dying, and which of those failures can I recover?”
If the transaction fails, the business loses a payment attempt from someone who was ready to buy.
Payment success rate (PSR) measures how many attempted payments complete successfully. But the useful question is not only, “What is my PSR?” It is “Where are the failed attempts dying, and which of those failures can I recover?”
TL;DR
- Payment success rate is the percentage of attempted payments that complete successfully.
- Calculate it as successful payment attempts ÷ total payment attempts × 100.
- Do not judge PSR using one universal benchmark. Compare it by country, issuer, payment method, transaction value and first attempt vs retry.
- Improving PSR requires different fixes for issuer declines, authentication failures, technical errors, fraud false positives and temporary declines.
What is the payment success rate?
Payment success rate tells you how effectively your payment infrastructure turns attempted transactions into completed payments.
If customers make 1,000 valid payment attempts and 900 succeed:
Payment Success Rate = (900 ÷ 1,000) × 100 = 90%
The metric matters especially for ecommerce, SaaS, travel, edtech and other businesses accepting international payments.
However, PSR should not be confused with checkout conversion rate.
Checkout conversion asks: *How many checkout sessions became orders?*
Payment success rate asks: *Of the payment attempts that were actually submitted, how many succeeded?*
How to calculate payment success rate?
The basic payment success rate formula is:
Payment Success Rate = (Successful Payment Attempts ÷ Total Payment Attempts) × 100
But your denominator matters.
If the same customer retries a card three times, should that count as one customer journey or three payment attempts?
| Metric | What it tells you |
|---|---|
| Overall PSR | Success across every submitted attempt |
| First-attempt PSR | How often customers succeed without retrying |
| Retry recovery rate | How many initially failed payments are later recovered |
| Value-weighted PSR | Share of attempted payment value successfully captured |
Transaction-count PSR can look healthy while large failed payments still create meaningful revenue loss, so payment value matters too.
Where does a failed payment actually fail?
1. The payment never reaches the issuer
Some failures happen before the issuing bank can even approve or decline the transaction.
Causes can include:
- gateway or acquirer outages
- API errors
- timeouts
- network failures
- malformed transaction data
2. The issuer declines the transaction
The issuing bank may decline a payment because of:
- insufficient funds
- card restrictions
- suspected fraud
- transaction limits
- geographic or merchant-category controls
- other issuer risk decisions
A merchant or gateway cannot override an issuer decline. The next step is identifying whether it is hard or potentially recoverable.
3. Authentication fails
International card payments may require 3D Secure authentication.
The transaction can fail because the customer:
- abandons the challenge
- enters incorrect authentication information
- times out
- encounters an issuer authentication problem
4. Fraud controls block a genuine customer
Fraud screening is necessary, but overly aggressive rules can create false positives.
The objective is not maximum approvals at any cost; it is better separation of good and bad transactions.
5. A temporary failure is treated as permanent
Not every decline should be retried.
Intelligent retry logic should therefore respond to the decline reason instead of repeatedly resubmitting every failed payment.
How to improve your payment success rate?
Fix technical failures first
Track gateway errors, acquirer availability, latency and timeouts.
Improve payment routing
If your provider supports multiple acquiring routes, transactions can be routed using factors such as issuer, network, geography and real-time route performance.
Optimise 3DS authentication
Monitor:
- frictionless vs challenge flows
- challenge completion
- authentication failure codes
- issuer-specific problems
Do not treat every 3DS failure as a generic card decline.
Retry selectively
Use retries for recoverable failures rather than hard declines.
Review fraud false positives
Compare rejected transactions against chargebacks, issuer responses and customer-support cases.
Give customers another route
If a card cannot be completed, another payment method can preserve the sale.
Depending on the market, this can include:
- another card
- Apple Pay or Google Pay
- a relevant local payment method
- bank-based collection for invoice-led payments
What should you track alongside payment success rate?
A useful PSR dashboard should include:
- first-attempt PSR
- overall PSR
- retry recovery rate
- issuer-decline rate
- technical-error rate
- authentication completion rate
- fraud rejection rate
- payment success by country
- payment success by issuer/BIN
- payment success by card network or payment method
- payment success by acquirer/route
- value-weighted PSR
Improve international payment success with PayGlocal
PayGlocal currently advertises up to 96% payment success rate on international payments.
Its cross-border payment stack combines:
- intelligent routing and payment orchestration
- issuer-level optimisation
- 3DS optimisation
- real-time fraud scoring
- international cards
- Apple Pay and Google Pay
- alternate payment methods
- recurring payments with retry logic
Codeyoung, for example, reports that its international payment success rate increased from 75% to 95% with PayGlocal.
The goal is not simply to retry more transactions. It is to identify why each payment failed and give recoverable transactions a better path to approval.
