Do you refund unhappy users yourself, or wait for them to file a chargeback?
Something I only learned recently from a friend’s startup: when a customer is annoyed and can’t find how to cancel, they don’t always email you. A lot of them just call their bank and dispute the charge.
His product was $12/month. A handful of people forgot about an annual renewal, got charged, and went straight to their banks. Each dispute meant losing the payment, plus a dispute fee on top, which was more than the cost of the plan itself. Then he found out that if your dispute rate creeps up toward 1% or so, payment processors can start putting restrictions on your account, or even shut it down. For a small product with a few hundred customers, 3 or 4 disputes can already be a scary percentage.
What got me is that this is such a boring, unwanted problem that nobody talks about it. We obsess over growth, features and pricing pages, but the thing that can freeze your revenue is some random person who didn’t recognize “ACME LLC*SUB” on their statement.
Things he changed afterwards, and which I’m copying for my own project:
Made the billing descriptor match the product name people actually know
Sends a reminder email a few days before any annual renewal
Put the cancel button where people can see it, no “contact us to cancel” nonsense
Refunds first and asks questions later for anything small, since a $12 refund is cheaper than a $12 dispute plus the fee
Support email is in the footer of every receipt
I’m still not sure how generous a refund policy should be for early stage products. Too strict and you get disputes, too loose and people might take advantage.
What’s your refund policy, and has it ever been abused? Has anyone here actually had a payment account frozen or restricted? And how do you handle annual plans, since those seem to cause the most chargebacks?
p/runevr
p/aperture-7
p/producthunt
p/google-cloud-platform
p/raycast
p/kuc-kuc
p/lasso-11
p/kodlo
p/offiai
p/ai-context-flow
p/many-displays
p/reso
p/dino-kids
p/dex-by-exmergo
p/htmldrag
p/jev
p/supabase
p/murror
p/nexupira
p/jot-2-0
Replies
One technical half of "refund first" that is easy to miss: make sure the refund actually reaches your product. On my app's web purchases, the subscription platform I use did not apply refunds of one time purchases made through Stripe Checkout. A live refund left the user's profile still marked as not refunded, with no event at all. So refunds come straight from Stripe's charge.refunded webhook now, and it takes back exactly what the purchase gave: a cloned voice is revoked, a credit pack is subtracted, floored at zero so credits already spent stay spent. Each refund is applied once, keyed by the charge. Without that, generous refunds quietly turn into free products.