Stripe Webhook Delivery and Event Processing Reliability Audit
Check that payment events reach and update the application.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit webhook reliability. Webhook endpoints and the events they receive: [ENDPOINTS_AND_EVENTS]. Delivery log summary for 30 days: attempts, successes, failures, retries and response times: [DELIVERY_LOG]. How my application handles duplicates and order: [HANDLING_DESCRIPTION]. Orders or subscriptions that were out of step with payments: [MISMATCH_EXAMPLES]. Separate delivery problems (Stripe to me) from processing problems (inside my application). Calculate delivery success rate, the share of events needing retries, median and slowest response time, and mismatches between payments and my records, with arithmetic. Check signature verification, idempotency (processing each event ID once), out-of-order events, timeouts and alerting. Mismatch table with Order or subscription, Stripe event, Time received, Processed yes or no, and Cause, with the fix: handle retries without duplicating, respond quickly then process asynchronously, verify the signature before using the payload, and fetch the object's current state when order matters. Signing secrets belong in a secrets store, never pasted into chats or code. Return fixes in priority order, a daily reconciliation job in plain words (list payments from the last day via the API, compare with the application's records, email differences), an alert (if failed deliveries exceed a set level for 15 minutes, page the owner), a runbook (find affected orders, replay events safely, inform customers), and a deployment checklist with a replay of test events. Test-mode drill: send an event twice and confirm it is processed once; send events in reverse order and confirm the final state is correct; stop the endpoint for ten minutes, restore it, and confirm missed events are delivered and processed [VERIFY retry behaviour]. Mark dashboard names [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.