Stripe Webhook Tester
Capture and inspect real Stripe payment events — payment_intent.succeeded, checkout.session.completed, and more — without CLI or tunnel setup.
Quick Answer
Go to requex.me, copy your unique URL, paste it into the Stripe dashboard under Developers → Webhooks, then send a test event. You'll see the full payload — including the Stripe-Signature header — in real time, with no installation required.
How to Test Stripe Webhooks with Requex
- 1
Generate your Requex URL
Open requex.me. A unique HTTPS endpoint is generated immediately — no signup, no install. Copy the URL from the top of the page.
- 2
Add it as a Stripe webhook endpoint
In Stripe Dashboard → Developers → Webhooks → Add endpoint. Paste your Requex URL and select the event types you want to capture (e.g.
payment_intent.succeeded). Use test mode for development. - 3
Trigger a test event
In the Stripe webhook endpoint view, click "Send test webhook" and choose an event type. Stripe will deliver a realistic test payload to your Requex URL.
- 4
Inspect the full payload
Requex shows every detail in real time: the event type, the
Stripe-Signatureheader, all other headers, and the full JSON body. Copy the body to start building your handler.
Stripe Event Types to Test
| Event Type | When It Fires | Common Use |
|---|---|---|
| payment_intent.succeeded | Payment confirmed | Fulfil order, send receipt |
| payment_intent.payment_failed | Payment declined | Notify customer, retry |
| checkout.session.completed | Checkout flow complete | Provision access, send email |
| customer.subscription.created | New subscription | Activate plan, update DB |
| customer.subscription.deleted | Subscription cancelled | Downgrade access, notify |
| invoice.payment_failed | Recurring payment fails | Dunning flow, suspension |
| charge.refunded | Refund processed | Update order status, notify |
The Stripe-Signature Header
Every Stripe webhook includes a Stripe-Signature header containing a timestamp and HMAC-SHA256 signature. In production, your handler must verify this using your webhook signing secret via stripe.webhooks.constructEvent().
Requex displays this header in full so you can see exactly what Stripe sends. When you're ready to verify signatures, the Stripe CLI's stripe listen command injects the correct signature automatically.
Common Issues
Stripe shows "Failed to send test webhook"
This usually means Requex returned a non-2xx response. Check the Settings tab on your Requex dashboard and ensure the response config is set to return 200 OK.
Webhook not appearing in Requex
Ensure you're looking at the same Requex tab where you copied the URL — each tab has a unique endpoint. If you closed and reopened the tab, the ID may have changed.
Want to test signature verification locally
Use the Stripe CLI (stripe listen --forward-to localhost:3000/webhook) instead of Requex. The CLI injects a valid signature automatically, so constructEvent() works without extra steps.
Related Resources
Start Testing Webhooks Now
Generate your unique URL and test webhooks instantly. Free, no signup.
Open Webhook Tester →