---
title: "Stripe Webhook Tester — Test & Inspect Online | WebhookRelay"
meta:
  "og:description": "Test and inspect Stripe webhooks online with a free webhook tester URL — capture real Stripe payloads, read the signature header, then forward locally."
  "og:title": "Stripe Webhook Tester — Test & Inspect Online"
  description: "Test and inspect Stripe webhooks online with a free webhook tester URL — capture real Stripe payloads, read the signature header, then forward locally."
---

![Stripes](https://webhookrelay.com/blog/stripe-webhook-tester/images/stripes.svg)

# **Stripe Webhook Tester — Test & Inspect Online**

Test and inspect Stripe webhooks online with a free webhook tester URL — capture real Stripe payloads, read the signature header, then forward locally.

![Stripe Webhook Tester — Test & Inspect Stripe Webhooks Online](https://webhookrelay.com/blog/stripe-webhook-tester/images/blog/heroes/tester.jpg)

If you are wiring up Stripe webhooks, the first question is always the same: _what does Stripe actually send?_ The docs show an idealised payload, but the real request — its headers, its `Stripe-Signature` header, the exact JSON shape — is what your handler has to parse. A **Stripe webhook tester** gives you a public URL that captures those real requests so you can read every byte before you write any code.

## [Get a free Stripe webhook tester URL](#get-a-free-stripe-webhook-tester-url)

The fastest way is our free [Webhook Bin](https://webhookrelay.com/blog/stripe-webhook-tester/webhook-bin/) — a no-code [webhook tester](https://webhookrelay.com/blog/stripe-webhook-tester/webhook-bin/) that gives you an instant public URL and stores every request that hits it, headers and body included. No signup, no deploy:

1. Open the [Webhook Bin](https://webhookrelay.com/blog/stripe-webhook-tester/webhook-bin/) and copy the URL it generates for you.
2. In **Developers → Webhooks in the Stripe Dashboard**, add a webhook endpoint and paste that URL.
3. Trigger an event (see below) and watch the request land in the bin in real time.

Because the bin keeps the full request, you can inspect the `Stripe-Signature` header, the `Content-Type`, and the complete payload — the three things you need to build and verify a handler.

## [What a Stripe webhook looks like](#what-a-stripe-webhook-looks-like)

Stripe delivers webhooks as an HTTP POST with a `application/json` body. Stripe lets you fire test events straight from the dashboard or with the Stripe CLI, so you can replay a real `payment_intent.succeeded` into your bin and read every field it actually sends.

A typical `payment_intent.succeeded` payload looks like this:

```
{
  "id": "evt_1P...",
  "object": "event",
  "type": "payment_intent.succeeded",
  "data": {
    "object": {
      "id": "pi_3P...",
      "object": "payment_intent",
      "amount": 1999,
      "currency": "usd",
      "status": "succeeded"
    }
  }
}
```

Common Stripe events you will want to test:

- `payment_intent.succeeded`
- `checkout.session.completed`
- `customer.subscription.updated`
- `invoice.paid`

## [Verifying the Stripe signature](#verifying-the-stripe-signature)

Stripe signs each request so you can prove it really came from Stripe. The signature travels in the **`Stripe-Signature`** header and is HMAC-SHA256 computed over `timestamp.payload`, using a signing secret that starts with `whsec_`. Capture a real request first, then use our [HMAC signature verifier](https://webhookrelay.com/blog/stripe-webhook-tester/hmac-verification/) and the [verify a webhook signature](https://webhookrelay.com/blog/stripe-webhook-tester/blog/verify-webhook-signature/) guide to confirm your verification logic against a payload you can actually see.

## [From inspecting to receiving on localhost](#from-inspecting-to-receiving-on-localhost)

A bin is perfect for _seeing_ the payload. When you are ready to drive your **local** handler with real Stripe events — without deploying — forward them straight to `localhost` with the Webhook Relay agent. The full walkthrough is here: [Receive Stripe webhooks on localhost](https://webhookrelay.com/blog/stripe-webhook-tester/blog/receiving-stripe-webhooks-localhost/).

That gives you a stable public URL that tunnels to your machine, so Stripe keeps delivering to the same endpoint while you iterate on `localhost`, no firewall changes or public IP required.

## [Test Stripe webhooks online in three steps](#test-stripe-webhooks-online-in-three-steps)

1. **Capture** — point Stripe at a [Webhook Bin](https://webhookrelay.com/blog/stripe-webhook-tester/webhook-bin/) URL and inspect the real request.
2. **Verify** — confirm the `Stripe-Signature` header with the [HMAC verifier](https://webhookrelay.com/blog/stripe-webhook-tester/hmac-verification/).
3. **Forward** — when the shape is clear, [receive Stripe webhooks on localhost](https://webhookrelay.com/blog/stripe-webhook-tester/blog/receiving-stripe-webhooks-localhost/) and build your handler.

New to webhooks in general? Start with [what is a webhook](https://webhookrelay.com/blog/stripe-webhook-tester/blog/what-is-webhook/) and [how to test webhooks](https://webhookrelay.com/blog/stripe-webhook-tester/blog/how-to-test-webhooks/).

Ready to inspect your first Stripe event? [Open a free Webhook Bin](https://webhookrelay.com/blog/stripe-webhook-tester/webhook-bin/) and paste the URL into Stripe.