Stripe webhook event decoder

Paste a Stripe event to see what happened in plain English, which fields matter for that event type, and how ChargeBell would post it in Slack. Amounts and dates are converted for you.

Runs in your browser. Nothing you paste is sent or saved.

Load a sample

Paste the whole event, or just its data.object. Copy it from Workbench or the Events page in the Stripe Dashboard, the Stripe CLI, or your webhook logs. Events can include customer names, emails, and addresses, so treat them like customer data.

What happened

Test modepayment_intent.succeeded

jamie@example.com paid $249.00.

  • A PaymentIntent event doesn't include the card. latest_charge holds the charge ID, and the charge has the card brand and last 4.
Event ID
evt_3ExamplePaymentSucceeded01
Created (UTC)
Sep 29, 2026, 2:14 PM UTC
API version
2026-09-30.endive
Object (payment_intent)
pi_3ExamplePaymentIntent0001

Key fields

The fields that matter for this event type. Amounts are in the currency's smallest unit; times are Unix seconds.

data.object.idpi_3ExamplePaymentIntent0001
The PaymentIntent ID. Use it to find the payment in Stripe.
data.object.amount_received24900 ($249.00)
What was actually collected, in the currency's smallest unit.
data.object.amount24900 ($249.00)
The amount the payment was created for.
data.object.currencyusd
Three-letter ISO currency code, lowercase.
data.object.statussucceeded
succeeded means the funds are captured.
data.object.customercus_ExampleJamie01
The Stripe customer ID, if the payment has one.
data.object.receipt_emailjamie@example.com
Where Stripe sends the receipt, if set.
data.object.latest_chargech_3ExampleCharge000001
The charge for this payment. It has the card details and the balance transaction with fees.
data.object.payment_methodpm_1ExampleVisa4242
The PaymentMethod ID used to pay.
data.object.descriptionOrder #1042
Your own description of the payment.
data.object.metadata{"order_id":"1042"}
Key-value data your integration attached.

In Slack with ChargeBell

How ChargeBell would post this event. Times are shown in UTC here; ChargeBell uses your workspace's time zone.

ChargeBellAPP2:14 PM

🔔 You got paid: $249.00

jamie@example.com

Amount (before fees)
$249.00

Order #1042

View in Stripe

With fee lookup on, ChargeBell shows gross, Stripe fee, and what you keep. The same event can post as a first payment, big payment, or recovered payment alert instead.

Read the guide to payment received alerts in Slack.

Common Stripe webhook events

The events most SaaS teams listen to. Stripe documents every type in its event types reference.

payment_intent.succeeded
A payment went through and the money is captured.ChargeBell alert: Payment received. See the guide
payment_intent.payment_failed
A payment attempt failed, usually a card decline. last_payment_error says why.ChargeBell alert: Payment failed. See the guide
charge.succeeded
The charge behind a payment succeeded. Carries card brand, last 4, and risk outcome.
charge.refunded
A charge was fully or partly refunded.ChargeBell alert: Refund sent. See the guide
charge.dispute.created
A customer disputed a charge with their bank. There is a deadline to respond.ChargeBell alert: Charge disputed. See the guide
invoice.paid
An invoice was paid, by a successful charge or marked paid outside Stripe.ChargeBell alert: Invoice paid. See the guide
invoice.payment_failed
An invoice payment attempt failed. Stripe may retry it on a schedule.
customer.subscription.created
A customer started a subscription, paid or on a trial.ChargeBell alert: New subscriber. See the guide
customer.subscription.updated
Something on a subscription changed: plan, quantity, status, or a scheduled cancellation.ChargeBell alert: Plan upgraded or downgraded.
customer.subscription.deleted
A subscription ended. It is canceled and won't bill again.ChargeBell alert: Subscription canceled. See the guide
customer.subscription.trial_will_end
A trial ends in three days, or right away if the trial was ended early.ChargeBell alert: Trial ending soon.
payout.paid
Stripe expects a payout to have reached your bank account.ChargeBell alert: Payout marked paid. See the guide
payout.failed
A payout to your bank failed and the money returned to Stripe.ChargeBell alert: Payout failed.
checkout.session.completed
A customer finished a Stripe Checkout page.

How Stripe webhook events are structured

Every event has the same envelope. Only data.object changes shape, depending on the type. Before you trust a payload, check its signature as described in Stripe's webhook guide.

{
  "id": "evt_...",
  "object": "event",
  "type": "invoice.paid",
  "api_version": "2026-09-30.endive",
  "created": 1790575331,
  "livemode": false,
  "data": {
    "object": { "id": "in_...", "object": "invoice", ... },
    "previous_attributes": { ... }
  },
  "pending_webhooks": 1,
  "request": { "id": null, "idempotency_key": null }
}
id
The event's own ID, starting with evt_. Use it to skip duplicate deliveries.
type
What happened, such as invoice.paid. Route your handler on this.
data.object
The object that changed, as it was when the event happened.
data.previous_attributes
On *.updated events only: the old values of the fields that changed.
created
When the event was created, in Unix seconds (UTC).
livemode
true for live mode, false for test mode.
api_version
The API version used to render data.object.
account
The connected account ID, on Connect events only.

Stripe webhook questions

How do I verify a Stripe webhook signature?

Stripe signs each delivery with your endpoint's signing secret, which starts with whsec_. The Stripe-Signature header holds a timestamp (t) and an HMAC-SHA256 signature (v1) of the timestamp and the raw request body. Pass the raw body, the header, and the secret to your Stripe library's webhook helper, which recomputes the signature and rejects old timestamps (5 minutes by default). Verify before you parse or trust the JSON. This decoder doesn't check signatures, because that needs your secret, and you shouldn't paste it anywhere.

Why are Stripe amounts in cents?

Stripe sends every amount as an integer in the currency's smallest unit, which avoids rounding errors. 24900 in USD is $249.00. Zero-decimal currencies such as JPY and KRW have no smaller unit, so 5000 in JPY is ¥5,000. The decoder applies Stripe's currency rules when it converts amounts.

What's the difference between payment_intent.succeeded and charge.succeeded?

A PaymentIntent tracks the whole payment, including retries and authentication. A charge is a single attempt to move money. When a payment succeeds you get both events. payment_intent.succeeded is the one to act on for fulfillment. charge.succeeded carries details the PaymentIntent event doesn't, such as card brand, last 4, risk outcome, and the balance transaction with fees.

How do I tell test events from live events?

Check livemode at the top of the event: true is live, false is test mode or a sandbox. Test and live endpoints have different signing secrets, and test data never moves real money. The decoder shows a Test mode or Live mode label for every event.

Why doesn't my event match the API reference?

Stripe renders data.object with the API version shown in api_version, which is your account's default version or the version set on the webhook endpoint. The payload never changes after the event is created. Fields move between versions: since 2025-03-31, invoices link their subscription under parent.subscription_details and billing periods live on subscription items.

Get the events that matter posted to Slack.

ChargeBell listens to your Stripe account and posts payments, failed payments, disputes, cancellations, and payouts to the Slack channels you choose.

Create your workspace