Workflow · Customers · Opening soon

Involuntary churn and failed payment recovery

See which failed subscription payments recovered on retry, and which customers churned because the card failed. Use this month’s Stripe invoices and subscriptions, with status, amount, and date.

Book a demo

Someone typed

“show this month’s stripe invoices and subscriptions, with status Agrees when payment went through, otherwise Retry failed, Canceled, or Churned, plus the amount and date”

The agent read it as

show this month’s Stripe invoices and Stripe subscriptions, with status Agrees when payment went through, otherwise Retry failed, Canceled, or Churned, plus the amount and date

What the agent built

3 steps, each one an ordinary Mammoth step you can open and change.

File

Stripe invoices

CSV export · 18 rows

File

Stripe subscriptions

CSV export · 15 rows

Step

Keep this month

Step 1

Join

Add subscription status

16 of 16 paired

Step

Set final status

Step 3

Result

Stripe billing status

16 rows · 5 flagged

Schedule

Runs when you say

Proposed

File
Stripe invoices
CSV export · 18 rows
File
Stripe subscriptions
CSV export · 15 rows
Step
Keep this month
Step 1
Join
Add subscription status
16 of 16 paired
Step
Set final status
Step 3
Result
Stripe billing status
16 rows · 5 flagged
Schedule
Runs when you say
Proposed

Checked on the sample files: every step ran, 16 rows came out, and the join paired 16 of 16 rows.

Download Stripe invoices sample (18 rows)Stripe Dashboard: Billing > Invoices > Export
Download Stripe subscriptions sample (15 rows)Stripe Dashboard: Billing > Subscriptions > Export

What you get back

The result of that run, the rows to look at first.

Stripe billing statusSample data16 rows

11 agrees3 canceled2 churned

Invoice id	Subscription id	Status	Amount	Date
in_1003	sub_03r8s2	Canceled	6,200	2026-10-14
in_1005	sub_05v9w3	Churned	5,400	2026-10-13
in_1009	sub_09d3e7	Canceled	5,600	2026-10-16
in_1012	sub_12k4l6	Churned	4,500	2026-10-21
in_1014	sub_14p2q5	Canceled	8,800	2026-10-22
in_1001	sub_01n7xk	Agrees	4,900	2026-10-03
in_1002	sub_02p4qz	Agrees	7,500	2026-10-03
in_1004	sub_04t6u1	Agrees	8,800	2026-10-06
in_1006	sub_06x2y5	Agrees	3,100	2026-10-07
in_1007	sub_07z4a8	Agrees	6,700	2026-10-09
in_1008	sub_08b1c6	Agrees	4,200	2026-10-09
in_1010	sub_10f5g9	Agrees	9,800	2026-10-13

16 rows in the result · 12 shown, problems first. Sample data: illustrative figures, not business results.

How do you track involuntary churn from failed payments?

Export this month’s Stripe invoices and subscriptions, then keep only this month’s rows. Add the subscription status, then set a final status for each row, such as Agrees, Retry failed, Canceled, or Churned.

How it works

How to use the Stripe billing status workflow

1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and checked on the sample files.
2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
3Change it in words, then turn it onSay what to change and see the new result before anything saves. Then choose when it runs.

Stripe billing status: questions

Which Stripe export should you use?

Use Stripe invoices and Stripe subscriptions exports for the same month. The workflow reads the exported file and uses the row data to check payment status and subscription status.

What happens to rows that do not match the rules?

Rows that do not match a rule keep their existing values or stay unclassified, depending on the step. You can then review them and decide whether they need a new rule or a manual check.

How do you change the rules in words?

Edit the step text to describe the rule differently, for example by changing which statuses count as recovered, failed, canceled, or churned. Then run the workflow again on the export.