Test your Stripe webhook integrations without the CLI. Inspect event payloads, verify signatures against your signing secret, and debug deliveries, all client-side.
No sign-up
Free
Runs in your browser
Webhook payload
Delivery log(mock data)
Event
Delivered
Status
Attempts
succeeded
2 min ago
Delivered
1
refunded
18 min ago
Delivered
1
customer.subscription.created
1 hr ago
Failed
3
payment_succeeded
3 hrs ago
Delivered
1
payment_failed
5 hrs ago
Delivered
2
Built by Witsberry
Building with Stripe webhooks?
Witsberry builds production-ready Stripe integrations (webhooks, billing, subscriptions, and refunds) with proper signature verification and idempotency from day one.
Stripe signs every webhook payload with a secret key unique to your endpoint. The signature header follows the format `t=timestamp,v1=signature` where `signature` is an HMAC SHA256 hash of the timestamp and payload body, using your webhook signing secret as the key. This tool lets you paste any payload and signature, provide your secret, and verify them without needing the Stripe CLI.
No. All signature verification happens entirely in your browser. Your webhook secret is never stored, transmitted, or logged anywhere. It is used only to compute the HMAC locally for comparison.
A failed verification usually means one of three things: (1) The payload was modified after Stripe sent it, even a whitespace change will break the signature. (2) The wrong webhook secret is being used, each endpoint has its own secret in the Stripe dashboard. (3) The signature header was altered or malformed. If verification fails unexpectedly, re-download the raw payload from your Stripe dashboard and try again.
In the Stripe dashboard, go to Developers → Webhooks → select your endpoint → under "Signing secret", click "reveal". Each endpoint has a unique secret starting with `whsec_`. You can also use the Stripe CLI: `stripe listen --forward-to localhost:3000/api/webhooks/stripe` which prints the secret automatically.
Common essential events include: `payment_intent.succeeded` (confirm payment), `payment_intent.payment_failed` (handle failure), `customer.subscription.created` (activate access), `customer.subscription.deleted` (revoke access), `invoice.payment_succeeded` (renew billing), `invoice.payment_failed` (dunning). For e-commerce, also handle `charge.refunded`. The specific events depend on your business logic.
Yes. This tool lets you paste webhook payloads and verify signatures without any CLI. For full local testing with live webhook delivery, you would normally need the Stripe CLI (`stripe listen`) or a tunneling tool like ngrok. This tool is ideal for debugging captured payloads from your Stripe dashboard or logs, and verifying your signing setup.