Workflow · Reconcile · Opening soon

Refunds by reason

Track refunds by month and reason from your Stripe refunds export. Then compare them with sales from the original Stripe charges export to calculate refund rate.

Book a demo

Someone typed

“show refunds by month and reason from the stripe refunds, and refund rate using sales from the original stripe charges month; include the monthly reason mix and the refund rate”

The agent read it as

Show refunds by month and reason from the Stripe refunds, and refund rate using sales from the original Stripe charges month; include the monthly reason mix and the refund rate, grouping by original charge month and calculating refund amount / sales amount.

What the agent built

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

File

Stripe refunds

CSV export · 15 rows

File

Stripe charges

CSV export · 18 rows

Step

Calculate monthly sales

Step 1

Step

Keep successful refunds

Step 2

Join

Bring in original charge month

15 of 15 paired

Step

Calculate monthly mix and rate

Step 4

Result

Monthly Refund Mix

11 rows

Schedule

Runs when you say

Proposed

File
Stripe refunds
CSV export · 15 rows
File
Stripe charges
CSV export · 18 rows
Step
Keep successful refunds
Step 2
Step
Calculate monthly sales
Step 1
Join
Bring in original charge month
15 of 15 paired
Step
Calculate monthly mix and rate
Step 4
Result
Monthly Refund Mix
11 rows
Schedule
Runs when you say
Proposed

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

Download Stripe refunds sample (15 rows)Stripe: Payments > Refunds > Export
Download Stripe charges sample (18 rows)Stripe: Payments > All payments > Export

What you get back

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

Monthly Refund MixSample data11 rows

Charge month	Reason	Refund amount (USD)	Monthly reason mix (%)	Refund rate (%)	Total refunds (USD)	Sales amount (USD)
2026-08-01	duplicate	20	21.1	19.2	95	495
2026-08-01	requested_by_customer	75	78.9	19.2	95	495
2026-09-01	duplicate	40	22.2	17.3	180	1,040
2026-09-01	fraudulent	45	25	17.3	180	1,040
2026-09-01	requested_by_customer	95	52.8	17.3	180	1,040
2026-10-01	duplicate	30	7.7	29	388	1,338
2026-10-01	fraudulent	128	33	29	388	1,338
2026-10-01	requested_by_customer	230	59.3	29	388	1,338
2026-11-01	duplicate	12	3.9	23	307	1,332
2026-11-01	fraudulent	50	16.3	23	307	1,332
2026-11-01	requested_by_customer	245	79.8	23	307	1,332

11 rows in the result. Sample data: illustrative figures, not business results.

How do you analyse refunds by reason?

Export your Stripe refunds and Stripe charges as files, then upload them to Mammoth. The workflow keeps successful refunds, links each refund to the original charge month, and calculates monthly refund mix and refund rate as refund amount divided by sales amount.

How it works

How to use the Monthly Refund Mix 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.

Monthly Refund Mix: questions

Which export file should you use?

Use the Stripe refunds export for refund rows and the Stripe charges export for sales rows. The workflow uses the charge month from the original sale to work out refund rate by month.

What happens to rows that do not match?

Rows that do not match the rules are left out of the result for that step. For example, unsuccessful refunds or rows without the needed month or amount data will not be counted in the final table.

How do you change the rules?

Edit the step in words, such as which rows to keep, which month to group by, and which amounts to compare. Then run the workflow again with the updated rules.