Stripe: 7 weekly loops that catch the money leaking out

If you sell through Stripe, you probably watch one number: how much came in. The problem is that money rarely disappears all at once. It leaks slowly, through declined charges nobody retried, subscriptions overdue for two weeks, refunds that became a habit and disputes that missed the deadline.

None of these leaks shows up in today's balance. All of them show up when someone compares the week with the usual pattern and has a written threshold. That is what this guide gives you: 7 weekly loops, each with the number that triggers action, the path in the Stripe Dashboard and what to do when it fires.

Short answer: a weekly finance loop is a fixed check, done every Monday, that compares the week with the recent average and only calls you when a threshold is crossed. In Stripe, the 7 that pay off most are revenue, declined charges, overdue invoices, cancellations, refunds, disputes and ad spend against revenue.

How a weekly loop works

Every loop has four parts: the source (Stripe and, in loop 7, your ad accounts), the comparison (this week against the average of previous weeks), the threshold (the number that separates noise from a problem) and the task (who does what). If the threshold is not crossed, the loop stays quiet. That is what keeps the Monday meeting from turning into a report reading.

1. Weekly revenue below the usual

What to check: net revenue for the week that just closed against the average of the previous 4 weeks.

Threshold: a drop of 15% or more.

1. In the Stripe Dashboard, open Reports and then Financial summary (or the revenue view under Billing, if you sell subscriptions).
2. Select the last 5 weeks and group by week.
3. Add up the 4 previous weeks and divide by 4.
4. Compare with the week that closed. If the drop is above 15%, open loops 2 to 5 before blaming demand.

Result: you discuss the gap on Monday, not at month end.

2. Declined charges nobody retried

What to check: the share of this week's charges that ended with a failed status.

Threshold: more than 5% of the week's charges.

1. Open Payments and filter by Status: Failed for the last 7 days.
2. Write down the total and divide by the number of charges in the week.
3. Open 5 failures and read the decline reason (insufficient funds, expired card, suspected fraud).
4. Check in Billing settings that automatic retries and expired card emails are turned on.

Result: you recover sales that were already closed.

3. Invoice overdue for 7 days or more

What to check: subscriptions with an open invoice past its due date.

Threshold: any customer with an invoice overdue for 7 days or more.

1. Open Billing and then Invoices.
2. Filter by Past due and sort by due date.
3. Separate those past 7 days and cross them with each customer's monthly value.
4. Hand the list to whoever talks to the customer, starting with the highest value.

Result: you call before it turns into a cancellation. To see the impact over a year, learn how to calculate your customer retention rate.

4. Cancellations above normal

What to check: how many subscriptions were canceled this week against the average of the previous 8 weeks.

Threshold: 2 times the weekly average.

1. Open Billing, then Subscriptions, and filter by Canceled.
2. Count the cancellations for this week and the previous 8 weeks.
3. If it is above 2 times, read each cancellation reason (if you collect it) and the original plan.
4. Look for the common factor: same plan, same signup month, same price change.

Result: you find the reason while there is still time to keep the next ones.

5. Refunds becoming a habit

What to check: the amount refunded this week over the week's revenue.

Threshold: above 3% of the week's revenue.

1. Open Payments and filter by Refunded for the last 7 days.
2. Add up the amount and divide by the revenue from loop 1.
3. Group refunds by product.
4. Take the product with the most refunds to whoever handles delivery and to whoever sells it.

Result: a refund is a sign of a wrong product, delivery or sales promise. You find out which one.

6. New dispute

What to check: open disputes (chargebacks) and the month's dispute rate.

Threshold: any new dispute, or a rate above 0.5% of payments in the month.

1. Open Payments and then Disputes.
2. Filter by Needs response and note each deadline.
3. Gather evidence: proof of delivery, customer conversations, accepted terms.
4. Respond before the deadline from the Dashboard. A dispute without a response is a lost dispute.

Result: you do not lose the money through silence, and you see whether the month's rate is rising.

7. Ad spend against new revenue

What to check: how much you spent on Meta Ads and Google Ads this week against the new revenue that came into Stripe in the same week.

Threshold: spend above 30% of the week's new revenue. Adjust the number to your margin: with a 40% margin you cannot spend 30% on ads.

1. In Meta Ads Manager and Google Ads, pull spend for the last 7 days.
2. In Stripe, filter Payments for the same 7 days and separate new customers.
3. Divide total spend by revenue from new customers.
4. If it is above the threshold, review campaign by campaign before cutting everything.

Result: you see whether ads pay for themselves, in real money. To build the full view, see what to include in a business finance dashboard.

How to run the 7 loops without opening 3 dashboards every Monday

Done by hand, the set takes 40 to 60 minutes a week and depends on someone remembering. The alternative is to let an agent do the comparison and only bring what crossed the threshold. In Sherlok, you connect Stripe, Meta Ads and Google Ads once, and the Goals Agent compares the sources with the goals you wrote, while the Report Agent builds the weekly summary. In the current phase, the agent suggests and you execute.

If you already use Claude, you can ask the same questions there through the Sherlok connector (read only, works on the Free plan): "did this week's revenue drop more than 15% against the average of the previous 4?" The answer crosses Stripe and ads in a single analysis.

Frequently asked questions

Why weekly and not daily?

Revenue, cancellations and refunds swing a lot from one day to the next. Over a week, the noise evens out and the threshold starts to mean something. Disputes are the exception: check them more than once a week because of the deadline.

Do these thresholds work for any company?

They are starting points. Run 4 weeks, see how often each loop fired and adjust. If it fires every week, the threshold is too low. If it never fires, it is too high or the problem does not exist in your business.

Do I need a developer to automate this?

No. You can start with a spreadsheet and 7 rows. To remove the manual work, an agent connected to Stripe and your ad accounts does the comparison on its own and delivers only the tasks.

What changes on Monday

With the 7 loops written down, the Monday meeting stops being "how was the week?" and becomes "which thresholds were crossed and who fixes them". Most weeks, the answer is none or one. That is when the owner's time goes back to selling.