KPI Tree

Stripe Metric

Revenue

Failed Payment Rate = Failed Charges / Total Charge Attempts x 100

Failed Payment Analysis measures the volume and value of Stripe charges that do not succeed, broken down by the failure reason Stripe returns, such as insufficient funds, expired card, do not honour or fraud block. In Stripe data, each failed charge carries an outcome and a decline code, so the analysis groups failures by cause, card network, customer and whether the payment was a first attempt or a renewal. It turns raw failure events into a clear picture of how much revenue is at risk and which causes are recoverable.

Full guide: definition, formula, and benchmarks
StripeRevenue

Failed Payment Analysis

Failed Payment Analysis measures the volume and value of Stripe charges that do not succeed, broken down by the failure reason Stripe returns, such as insufficient funds, expired card, do not honour or fraud block. In Stripe data, each failed charge carries an outcome and a decline code, so the analysis groups failures by cause, card network, customer and whether the payment was a first attempt or a renewal. It turns raw failure events into a clear picture of how much revenue is at risk and which causes are recoverable.

How to calculate failed payment analysis

Failed Payment Rate = Failed Charges / Total Charge Attempts x 100

Why failed payment analysis matters for Stripe users

Not every failed Stripe charge is a lost sale. Soft declines such as insufficient funds or a temporary issuer block often recover on retry, while hard declines like a closed account rarely will. Without breaking failures down by decline reason, a team cannot tell how much of the lost revenue is genuinely recoverable, and it tends to either over invest in dunning or leave money on the table.

For subscription businesses this is the single largest driver of involuntary churn. Renewals that fail on an expired card look identical to a cancellation in the top line numbers, but the cause and the fix are completely different. Analysing failures by reason lets you target retries, card updater prompts and dunning emails where they actually move recovered revenue.

Understand and act on failed payment analysis with KPI Tree

Sync your Stripe charges, payment intents and balance transactions into your warehouse and compute Failed Payment Analysis in KPI Tree, grouping failed charges by decline code, card network and renewal versus first attempt. Place it in a metric tree alongside charge success rate and card decline rate so you can see how failure causes feed into recovered revenue and involuntary churn.

Assign RACI ownership so a payments or finance owner is accountable for the recoverable share, with revenue operations consulted on dunning changes. Set a weekly review cadence in KPI Tree to watch decline reason trends and confirm that retry and card update flows are closing the gap.

Get started with your Stripe data

Query using MCP
MCP

Pull metrics from Stripe directly through the Model Context Protocol.

Data Warehouse
SnowflakeBigQueryDatabricksRedshift

Connect your existing warehouse where Stripe data already lands.

Professional Services
FivetranSnowflakedbt

Our professional services team can build you turn-key AI foundations in a matter of weeks. Data warehouse on Snowflake/BigQuery, ELT with Fivetran, all modelled in dbt with a semantic layer.

Explore failed payment analysis across integrations

Empower your team to understand and act on Stripe data

Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.

Experience That Matters

Built by a team that's been in your shoes

Our team brings deep experience from leading Data, Growth and People teams at some of the fastest growing scaleups in Europe through to IPO and beyond. We've faced the same challenges you're facing now.

Checkout.com
Planet
UK Government
Travelex
BT
Sainsbury's
Goldman Sachs
Dojo
Redpin
Farfetch
Just Eat for Business