Can I use these payloads to test Stripe signature verification?

Not with this tool alone. The stripe-signature header here is a structurally valid placeholder, not a real HMAC, so stripe.webhooks.constructEvent() will reject it. Use the Webhook Header Emulator to compute a genuine HMAC-SHA256 signature over the same payload with your own signing secret.

How is this different from the Stripe CLI?

The Stripe CLI forwards real events from your Stripe test account and requires login plus a tunnel. This tool is account-free and instant: you edit the event body directly in the browser and get a shareable URL. The CLI is better for end-to-end verification; this is better for fast iteration on handler logic.

Are the event objects shaped like the real Stripe API?

Yes. The templates mirror the documented Stripe event envelope, including id, object, api_version, created, livemode, pending_webhooks, request, and a nested data.object carrying the invoice or charge. Amounts are integers in the smallest currency unit, as Stripe sends them.

~/tools / 01 / stripe-webhook-events

Stripe Webhook Event Mocker

Building a Stripe integration means handling webhooks long before real money moves. This tool ships editable, spec-shaped Stripe event envelopes — pick invoice.paid or charge.refunded, tweak the fields your handler cares about, and get a URL that replays the payload instantly. No Stripe CLI, no test-mode keys, no tunneling.

compose payload

template preset

status code latency (ms)

response body — live JSON editor

{
  "id": "evt_1PXaK2LkdIwHu7ixVp2qzLbT",
  "object": "event",
  "api_version": "2025-03-31",
  "created": 1751702400,
  "type": "invoice.paid",
  "livemode": false,
  "pending_webhooks": 1,
  "request": {
    "id": "req_9m4XKzT2ahF3Lo",
    "idempotency_key": null
  },
  "data": {
    "object": {
      "id": "in_1PXaJyLkdIwHu7ix8VQyWkbA",
      "object": "invoice",
      "customer": "cus_QOMx2mVYbXIfEB",
      "customer_email": "ada@example.com",
      "subscription": "sub_1PXaJxLkdIwHu7ixQ4C0f9nD",
      "status": "paid",
      "currency": "usd",
      "amount_due": 2900,
      "amount_paid": 2900,
      "amount_remaining": 0,
      "attempt_count": 1,
      "billing_reason": "subscription_cycle",
      "hosted_invoice_url": "https://invoice.stripe.com/i/acct_mock/test_mock",
      "lines": {
        "object": "list",
        "total_count": 1,
        "data": [
          {
            "id": "il_1PXaJyLkdIwHu7ixnbXm2ap4",
            "object": "line_item",
            "amount": 2900,
            "currency": "usd",
            "description": "Pro Plan — Jul 5 to Aug 5, 2026",
            "period": {
              "start": 1751702400,
              "end": 1754380800
            },
            "price": {
              "id": "price_1PXaJvLkdIwHu7ixMockPro",
              "unit_amount": 2900,
              "recurring": {
                "interval": "month"
              }
            },
            "quantity": 1
          }
        ]
      }
    }
  }
}

— validating —

exported mock url

—

▸ open mock ↗

simulated response headers

content-type: application/json

stripe-signature: t=1751702400,v1=mock_5257a869e7ecebeda32affa62cdca3fa51cad7e77a0e56ff536d0ce8e108d8bd

$ man stripe-events

Everything above is encoded into the #data= fragment of the exported URL — deflated and base64url-packed by your browser. Fragments are never sent to any server, so this mock is shareable and private. Paste the URL anywhere: a teammate's browser decodes it identically.

cat ./tldr.txt

A Stripe webhook event mocker generates the exact JSON envelope Stripe POSTs to your endpoint for events like invoice.paid and charge.refunded, so you can build and debug your handler without a Stripe account, test-mode keys, or the Stripe CLI listener running.

./when-to-use-this

Your handler needs to survive an invoice.paid event before billing code is finished, and you do not want to trigger real test charges to see the payload.
You are debugging a subscription lifecycle bug and need to replay the same event body repeatedly with one field changed.
A teammate reports a handler crash on charge.refunded — you need to share the exact payload that reproduces it.

./frequently-asked

Can I use these payloads to test Stripe signature verification?: Not with this tool alone. The stripe-signature header here is a structurally valid placeholder, not a real HMAC, so stripe.webhooks.constructEvent() will reject it. Use the Webhook Header Emulator to compute a genuine HMAC-SHA256 signature over the same payload with your own signing secret.
How is this different from the Stripe CLI?: The Stripe CLI forwards real events from your Stripe test account and requires login plus a tunnel. This tool is account-free and instant: you edit the event body directly in the browser and get a shareable URL. The CLI is better for end-to-end verification; this is better for fast iteration on handler logic.
Are the event objects shaped like the real Stripe API?: Yes. The templates mirror the documented Stripe event envelope, including id, object, api_version, created, livemode, pending_webhooks, request, and a nested data.object carrying the invoice or charge. Amounts are integers in the smallest currency unit, as Stripe sends them.

Stripe Webhook Event Mocker

cat ./tldr.txt

./when-to-use-this

./frequently-asked

grep -i related-searches

ln -s ./related-tools