Menu

Refunded or disputed, but the customer still has access? Your Stripe webhook only listens for the purchase
📰

Refunded or disputed, but the customer still has access? Your Stripe webhook only listens for the purchase

DEV Community: backend·WebhookProof·11 days ago
#PMtHKxN0
#devtobackend#devto#dev#charge#stripe
Reading 0:00
15s threshold

A lot of paywalls handle exactly one Stripe event. checkout.session.completed arrives, the handler sets paid = true , and that's the end of it. Nothing in the code ever sets it back.

So a refund goes out, or a customer's bank opens a dispute, or a subscription ends, and the database still says paid. The app keeps the door open for someone who's no longer paying. This post covers the events that should take access away, how to tie them back to the right user, and the edge cases worth deciding on up front. Every claim links to the doc it comes from (see Sources at the end).

How to tell if access is one-way

Open the webhook endpoint in the Stripe Dashboard and look at the events it's subscribed to. If the list is only checkout or payment-success events, Stripe never tells the app about refunds or disputes.

Refund a test-mode purchase, then reload the app as that test user.…

Continue reading — create a free account

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