MockCard

Stripe webhook health check

Paste your endpoint URL and MockCard runs real Stripe-shaped probes against it — free, no API key, no Stripe CLI.

Run free webhook checkRead API docs

What a Stripe webhook health check should cover

Production Stripe integrations must handle payment_intent.succeeded, payment_intent.payment_failed, and edge cases like unknown event types or malformed JSON. A health check should verify HTTP status codes, signature validation (if you use Stripe-Signature), and idempotent handling — not just that the URL returns 200.

How MockCard differs from Stripe CLI

Stripe CLI is excellent for forwarding live test events from your dashboard. MockCard is built for deterministic CI/CD and quick endpoint audits: fixed payloads, decline codes, 3DS next_action shapes, and optional HMAC signing with X-MockCard-Signature. You get a scored report in one POST — ideal before a deploy or when onboarding a new webhook route.

When to run this check

Run after changing webhook routes, middleware order, or queue workers. Also run when migrating from Stripe test mode to production — many teams discover their handler only tested happy-path events. Pair this page with chaos testing for duplicate delivery and delayed webhooks on Pro.

Webhook Health Check

See how your payment handler holds up against real failure scenarios — free, no signup

https://

Fires 5 probes · ~5 seconds · no account required

Frequently asked questions

Do I need a Stripe account?
No. MockCard sends test probes to your public HTTPS endpoint. Use a tunnel (ngrok, Cloudflare Tunnel) for localhost.
Does this validate Stripe-Signature?
The quick audit checks handler behaviour and HTTP responses. For full HMAC verification tests, use the API with your signing secret in CI.
How many free checks do I get?
Anonymous users get several audits per day; sign up free for 500 generations per month including webhook tools.

Related guides