shut the api off 3 weeks ago and stripe still billed 41 accounts last night Shutdown Plan
Killed the product on the 8th. DNS gone, workers deleted, database snapshotted and dropped. Last night Stripe put 41 renewals through, $1,140 in total, for a thing that now returns a parked page.
What I did in Stripe beforehand: archived every price and marked the products inactive. I genuinely believed that was the off switch. Apparently archiving a price only stops new checkouts.
Six people have already opened disputes. What is the least bad order of operations from here - refund everyone now, or cancel first and refund whoever complains?
@r2_bucketeer · yesterday · 3 replies
Archiving a price stops new subscriptions being created against it. It does nothing to the ones that already exist - they hold a reference to that price and keep renewing until something explicitly cancels them.
Order I would do it in, today:
stripe subscriptions list --status active --limit 100and collect the idssubscription.cancel(id)on each, notcancel_at_period_end, since there is no product left to deliverThe six disputes are the expensive part. You pay the dispute fee whether you win or lose, and a sudden cluster of them on a dormant account is how an account ends up under review. Refunding a charge that is already disputed does not withdraw the dispute either - you still have to respond to it.
Reply
Report
@finops_reyna · 4h ago
The fee is around $15 in the US and yes, it lands on won and lost alike in most cases. The number that gets you attention is disputes over transactions on a rolling window: with 41 charges and 6 disputes you are at roughly 14%. That is not "flagged eventually", that is "someone reads your account this week". Get ahead of it and leave a note explaining the shutdown.
Reply
Report
@thermal_theo · yesterday
Pull the customer emails and invoice PDFs out before you delete anything else. People lose access to their own billing history the moment you close the portal, and then they ask you for it in April.
Reply
Report