What it means
An online business sees customers reach payment but not complete orders, and a subscription company sees renewals fail with some recovered days later. Choose the unit before calculating, because a payment attempt can include retries for one invoice while a unique payment represents the customer obligation, and counting every retry can inflate failures compared with counting invoices that first failed.
A simple count-based failure rate is failed unique first attempts divided by all eligible unique first attempts, so if 40 of 1,000 first attempts fail, the rate is 4%. Stripe's recovery analytics defines subscription failure rate as the percentage of subscription payment volume that failed on the first attempt in its dashboard, and it separately measures recovered payments and recovery rate.
Payment-success and authorisation rates are also distinct, since Stripe describes a success-rate calculation including authentication failures and blocks while network authorisation looks only at attempts reaching card networks. Recoveries should not erase the initial failure metric, because a customer who succeeds after an email still encountered a problem while the final revenue loss may be zero, so report first-attempt failure and ultimate unrecovered amount separately.
Classify failure reasons, because insufficient funds, expired cards, incorrect details, authentication problems and technical errors need different responses. Look at where a payment failed, since an invalid form or fraud block occurs before an issuer decision while an issuer decline happens later, and improving a bank authorisation rate will not fix a broken checkout button that never submits an attempt.
Segment carefully, as new customers, renewal customers, card types, geography and payment method can have different patterns. Compare value as well as count, because ten failed large invoices can matter more to cash than a hundred small failures, so track failed payment amount, recovered amount and customer impact alongside the attempt rate.
For recurring billing, update card details and contact customers through legitimate, clear reminders; some retry timing can recover temporary failures, but endless retries can frustrate customers and incur fees. Do not assume every failure is the customer's fault, since a misconfigured merchant account, outdated payment integration or strict fraud rule can block good payments, and provider codes, logs and customer support evidence help investigate.
Protect payment data during diagnosis, because analysts can usually work with tokens, masked details and decline categories and should never ask customers to send complete card numbers or security codes through email to fix a failed purchase. Testing matters after a change, so if a new checkout reduces failures compare the same customer segments and periods where feasible.
Agree on a dashboard definition and keep it stable, noting any break in the series when a provider changes its metric or the business adds a payment method, since a neat trend line may otherwise hide a changed calculation. A payment failure is not the same as a refund or chargeback, so measure those events separately and do not let a team claim checkout success solved revenue leakage.
Escalate operational problems promptly, because a sudden spike in technical failures after a release may need rollback while a gradual increase in expired cards calls for different work. For a business owner, payment failure rate is an early warning, not a verdict: define the attempt, find the stage and cause, and track recovery as a separate outcome.
In practice
Real-world examples.
Example
A subscription team reports 40 failed first attempts out of 1,000 eligible invoices, then tracks how many recover later.
Example
A merchant sees issuer declines fall but checkout failures remain high because authentication fails before the network request.
Example
After changing fraud rules, the team compares acceptance by country and payment method rather than relying on one overall percentage.
Formula
Calculation
Count-based first-attempt failure rate = failed eligible unique first attempts / all eligible unique first attempts x 100. It is not a volume-weighted revenue-loss rate.
Worked example. Of 1,000 eligible first attempts, 40 fail, so the rate is 40 / 1,000 x 100 = 4%. Now weight by value: the 1,000 invoices total $250,000 and the 40 failed invoices total $12,000, so the value-based first-attempt failure rate is $12,000 / $250,000 x 100 = 4.8%.
Suppose $7,200 of the failed value is later recovered. The recovery rate is $7,200 / $12,000 x 100 = 60%, and the unrecovered amount is $12,000 - $7,200 = $4,800, which is $4,800 / $250,000 x 100 = 1.92% of attempted value. Reporting all three figures shows the initial problem, the recovery and the final loss separately.Case study
Seen in the real world.
This entirely fictional example concerns Blue Cedar Subscriptions, an invented service. Its dashboard called every retry a new failure and appeared to show a rising rate. Finance rebuilt the metric around unique invoices' first attempts and separately reported recovered value.
The team found an expired-card cluster and sent approved update reminders. It did not claim that those reminders would recover every invoice. The case illustrates measurement design, not a guaranteed revenue result.
Watch out
Common mistakes.
- Mixing first-attempt failures, retries and unrecovered invoices in one changing denominator.
- Treating issuer declines as the only cause while ignoring authentication, blocks and technical faults.
- Reporting a lower rate without checking whether payment mix or metric definitions changed.
Questions
People also ask.
What is payment failure rate?
It is the percentage of defined payment attempts that fail in a stated period.
Why does it matter for subscriptions?
Failed renewals can interrupt cash and create involuntary churn, even if some are later recovered.
How can it be reduced?
Diagnose failure stage and codes, then improve customer reminders, payment data and technical flow as appropriate.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%