Menu

Post image 1
Post image 2
1 / 2
0

Your Stripe webhook is going to silently drop a paid customer. Here are the 4 patterns that catch it before they chargeback.

DEV Community·Chalom Ellezam·18 days ago
#SVrZQwvm
#pattern#stripe#webdev#event#const#webhook
Reading 0:00
15s threshold

Disclosure: I'm a senior backend tech lead and I run HostingGuru. This article mentions HostingGuru once near the end. The four patterns below work on any platform, any framework, with any webhook provider (Stripe, GitHub, Twilio, Postmark). I want it useful even if you never become a customer. Two weekends ago a founder I do code reviews for sent me a panicked DM at 11pm: "A customer just opened a chargeback because we never unlocked their Pro plan. Stripe says the subscription is active. What's happening?" His webhook handler had crashed three days earlier at 3:14am on a Sunday. Stripe retried for 72 hours, gave up, marked the event as failed in their dashboard. Nobody was watching. The customer paid $49, got the same free-tier experience, asked for a refund, didn't get a fast reply, opened a dispute. By the time we caught it, his MRR was down one customer and his Stripe account had a $15 dispute fee on top. The fix took an hour. The damage took weeks to unwind.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More