Metric Definition
TSR
Track from
Transaction success rate
Transaction success rate is the percentage of attempted transactions that complete successfully out of all transactions attempted in a period. It is a core health signal for any business that processes payments or orders, because every failed transaction is revenue the customer wanted to give you but could not. A small move in this rate can shift revenue more than most growth campaigns.
7 min read
What is transaction success rate?
Transaction success rate is the proportion of attempted transactions that complete successfully. A transaction can fail for many reasons: a declined card, insufficient funds, a timeout between systems, a fraud rule that blocks a legitimate buyer, an expired session, or a network error at the payment gateway. Each failure is a transaction the customer intended to make but did not.
The rate matters because it sits directly on the revenue line. If you attempt 100,000 transactions in a month and 6,000 fail, you have a 94% success rate and 6,000 lost outcomes. Some of those buyers retry and succeed. Many do not. Unlike most operational metrics, a failed transaction is not a future risk, it is revenue that did not land today.
It is easy to treat a low success rate as a fixed cost of doing business. It rarely is. Most failures cluster into a handful of causes, and most of those causes respond to a specific fix. That is why the rate is worth decomposing rather than watching as a single line.
What counts as a transaction
Transaction success rate should count genuine attempts, not duplicate retries of the same intent. If a buyer is auto-retried three times and the third succeeds, count one successful transaction, not one success and two failures. Counting every retry as a separate attempt deflates the rate and hides whether the underlying problem is getting better.
How to calculate transaction success rate
Transaction Success Rate = (Successful Transactions / Total Transaction Attempts) x 100
For example, if a payments platform attempts 250,000 charges in a month and 235,000 complete, the success rate is 94%. The 15,000 failures are the number to break down, because the average rate hides very different failure profiles across card types, regions, and gateways.
The single number is the starting point, not the answer. Segment it before you act.
- 1
Count successful transactions
The number of attempts that completed and were authorised in the period. Exclude refunds and chargebacks, which are reversals of already-successful transactions, not new outcomes.
- 2
Count total transaction attempts
Every attempt made in the same period, successful and failed. Decide upfront whether auto-retries of the same intent count once or many times, and apply that rule consistently.
- 3
Divide and convert to a percentage
Successful transactions divided by total attempts, multiplied by 100. A rate of 0.94 becomes 94%.
- 4
Segment the result
Recalculate the rate by payment method, issuing region, device, and gateway. A healthy blended rate often hides one segment failing badly enough to drag the whole number down.
Transaction success rate in a metric tree
A metric tree turns transaction success rate from a number you watch into a structure you can act on. The headline rate is the root. Beneath it sit the stages where a transaction can fall over: authorisation, fraud screening, gateway routing, and customer-side input. Each branch points to a different owner and a different fix.
Metric tree insight
A drop in transaction success rate is almost never uniform. The tree localises it. If the fall is concentrated in fraud screening, the fix is rule tuning, not a new gateway. KPI Tree assigns RACI ownership to every node, so when the rate moves the accountable owner for that exact branch is notified, rather than the whole payments team debating a single blended number.
Transaction success rate benchmarks
What counts as good depends heavily on payment method, region, and the mix of card-present versus card-not-present volume. Card-not-present transactions fail more often than in-person ones, and cross-border transactions fail more often than domestic. Use these ranges as orientation, then judge yourself against your own segmented baseline.
| Context | Typical success rate | Notes |
|---|---|---|
| Domestic card payments | 95-98% | Local issuer relationships keep approval rates high. |
| Cross-border card payments | 85-92% | Foreign-issuer caution and currency rules lower approval. |
| Digital wallets | 97-99% | Tokenised credentials reduce input and expiry failures. |
| Subscription rebilling | 85-95% | Stored cards expire and lapse, so retry logic matters most. |
How to improve transaction success rate
Improving the rate is a question of finding which branch is leaking and applying the matching fix. Broad efforts rarely move the number. Targeted ones, aimed at the largest failure segment, almost always do.
Route intelligently across gateways
Send each transaction down the path most likely to succeed for that card type and region. Smart routing, with automatic failover when one gateway times out, recovers transactions that would otherwise be lost to a single point of failure.
Tune fraud rules to cut false positives
Overly strict rules block legitimate buyers. Measure your false-positive rate, not just your fraud catch rate, and loosen thresholds for low-risk segments. A single aggressive rule can cost more in lost sales than the fraud it prevents.
Retry declines on a smart schedule
For insufficient-funds declines, retry near typical payday dates rather than immediately. For expired cards, use account updater services so reissued cards charge without customer action.
Reduce checkout-side failures
Validate card details before submission, pre-fill where possible, and minimise friction in 3D Secure flows. Many failures never reach the issuer because the buyer mistyped a detail or abandoned an authentication step.
Common mistakes when tracking transaction success rate
- 1
Watching only the blended rate
A stable 94% can hide a region or card type collapsing to 70% while another improves. Always segment before you conclude the rate is healthy.
- 2
Counting retries as separate attempts
If auto-retries of one intent are each counted, the rate looks worse than reality and you cannot tell whether recovery logic is working. Decide the counting rule once and hold it.
- 3
Confusing declines with fraud blocks
An issuer decline and an internal fraud block need different fixes. Lumping them together points the team at the wrong lever.
- 4
Ignoring the recovery half of the picture
A 6% failure rate with strong retry recovery hurts revenue far less than a 4% rate with no recovery. Track recovered transactions alongside the headline rate.
Related metrics
Failed Payment Rate
Payment processing failure frequency
Financial Metrics
Metric Definition
Failed Payment Rate = (Failed Payment Attempts / Total Payment Attempts) x 100
Failed payment rate measures the percentage of attempted payment transactions that do not complete successfully. For subscription businesses, failed payments are the leading cause of involuntary churn, silently eroding revenue without any customer decision to leave. Reducing failed payment rate is one of the highest-leverage improvements a recurring-revenue business can make.
Checkout Conversion Rate
E-commerce metric
Ecommerce & Marketplace Metrics
Metric Definition
Checkout Conversion Rate = (Completed Purchases / Checkout Starts) x 100
Checkout conversion rate measures the percentage of users who begin the checkout process and successfully complete their purchase. It isolates the final stage of the buying funnel, from the moment a shopper initiates checkout to the order confirmation page. This metric is critical for e-commerce businesses because the checkout is where purchase intent is highest, and any friction at this stage directly destroys revenue that was nearly captured.
Chargeback Rate
Payment dispute frequency
Financial Metrics
Metric Definition
Chargeback Rate = (Number of Chargebacks / Total Transactions) x 100
Chargeback rate measures the percentage of transactions that customers dispute through their card issuer or bank. It is one of the most consequential financial metrics because exceeding card network thresholds can result in penalty fees, increased processing costs, or termination of the ability to accept card payments altogether.
Average Order Value
Revenue per transaction
Operations MetricsMetric Definition
AOV = Total Revenue / Number of Orders
Average order value measures the mean amount spent each time a customer places an order. It is a core e-commerce and retail metric that directly influences revenue, profitability, and customer acquisition efficiency.
Why did my metric change? A diagnostic framework
Metric Definition
When transaction success rate drops, this diagnostic framework helps you trace the decline back to the failing payment step or provider responsible.
Metric trees for fintech companies
Metric Definition
Transaction success rate sits at the heart of any payments business, and this guide shows how to place it within a wider fintech metric tree.
Find the branch that is costing you transactions
Build transaction success rate as a metric tree in KPI Tree, with the authorisation, fraud, routing, and checkout branches owned by the people who can fix them. When the rate moves, the accountable owner for that exact failure is notified, and a verified impact loop confirms the change worked.
