Source · Stripe · Verified November 1, 2026

Stripe webhook source guide

Short answer: A Hooks Stripe endpoint verifies Stripe-Signature as HMAC-SHA256 over <timestamp>.<raw body> with a five-minute tolerance, then normalizes each event to <resource>.<action> such as invoice.payment_failed.

Stripe events carry money-shaped fields that generic webhook tools flatten: amount, currency, customer, and a hosted invoice URL. Hooks keeps those on the subject, maps data.object.object to subject.kind, and deduplicates retried deliveries by the evt_ id.

Set up the webhook in Stripe

  1. In the Stripe Dashboard, open Developers → Webhooks → Add endpoint.
  2. Paste the endpoint's ingestion URL and select the events you need (invoice, checkout, subscription).
  3. Copy the endpoint's Signing secret (whsec_...) into the Hooks endpoint secret.
  4. Send a test event from the Stripe Dashboard and confirm it in the delivery log.

Signature verification

HeaderStripe-Signature: t=<timestamp>,v1=<hex>[,v1=...]
AlgorithmHMAC-SHA256 over <t>.<raw body>; any matching v1 signature passes.
Replay windowFive minutes between t and the current time.
Delivery idBody `id` when it starts with `evt_`, stable across Stripe retries.
  • The event type comes from X-Stripe-Event or the body type.
  • subject.title falls back through description, number, name, client_reference_id.
  • Hosted links are preferred: hosted_invoice_url, then receipt_url, url, short_url.

Events Hooks normalizes

event.typesubjectWhat it means
invoice.payment_failedinvoiceInvoice payment failed; amount and customer are mapped.
invoice.payment_action_requiredinvoiceSCA or manual action needed before the payment can complete.
invoice.paidinvoiceInvoice paid; amount_paid becomes subject.amount.
checkout_session.completedcheckout_sessionCheckout finished; receipt or short URL becomes the subject URL.
customer.subscription.createdsubscriptionSubscription created for a customer.
customer.subscription.deletedsubscriptionSubscription canceled; state reflects the final status.

Normalized payload

Every adapter produces this shape before filters or templates run. The raw payload and sanitized headers stay attached for audit, but filters and templates read the normalized fields.

Normalized event

{
  "id": "evt_01j9m6a1b2",
  "source": "stripe",
  "type": "invoice.payment_failed",
  "action": "payment_failed",
  "deliveryId": "evt_1PxYz2AbCdEfGhIj",
  "occurredAt": "2026-11-01T09:02:11.000Z",
  "actor": { "type": "application" },
  "subject": {
    "kind": "invoice",
    "id": "in_1PxYz2AbCdEfGhIj",
    "title": "Invoice INV-1042",
    "url": "https://invoice.stripe.com/i/acct_123/test_YWNjdF8x",
    "state": "open",
    "amount": 4900,
    "currency": "usd",
    "customer": "cus_PqRsTuVw"
  }
}

Filter and template examples

Filter: failed payments only

{
  "allow": [
    {
      "field": "event.type",
      "op": "in",
      "value": ["invoice.payment_failed", "invoice.payment_action_required"]
    }
  ]
}

Destination: Slack alert

{
  "mode": "chat",
  "token": "{{secret.SLACK_BOT_TOKEN}}",
  "channel": "C0123456789",
  "text": "Payment failed: {{event.subject.title}}\n{{event.subject.url}}"
}

Browse the raw payload and template samples for Stripe

Retries and the delivery log

408, 425, 429, and 5xx responses retry with backoff and honor Retry-After; other 4xx responses fail permanently with a named code. Every attempt keeps the rendered request and the target response, so a failure points at one field or one status instead of a guess.

Hooks delivery detail: attempt timeline, request payload, and the destination response for one delivery
Delivery detail: the attempt timeline, the rendered request the target received, and its response — the same record an event keeps for every destination.

Common errors

SymptomFix
SIGNATURE_INVALID after replaying an old requestStripe signatures expire after five minutes. Send a fresh test event instead of replaying a captured request.
Wrong secret: `whsec_...` vs the Stripe CLI secretThe CLI prints its own secret. Use the endpoint's Signing secret from Developers → Webhooks for production deliveries.
Amount looks 100x too largeStripe amounts are in the currency's minor unit. 4900 is $49.00; format it with the currency before display.

Pair with a target

Reference

Other sources

GitHubA Hooks GitHub endpoint verifies the X-Hub-Signature-256 HMAC on the raw body, stores the delivery, and normalizes each webhook into <event>.<action> (for example issues.opened) before any destination filter runs.SlackA Hooks Slack endpoint verifies X-Slack-Signature as HMAC-SHA256 over v0:<timestamp>:<raw body>, answers the url_verification handshake itself, and normalizes messages to app_mention.received or message.<channel_type>.LinearA Hooks Linear endpoint verifies Linear-Signature as hex HMAC-SHA256 over the raw body, rejects payloads whose webhookTimestamp is more than 60 seconds old, and normalizes events to issue.create, issue.update, and comment.create.SentryA Hooks Sentry endpoint verifies Sentry-Hook-Signature as hex HMAC-SHA256 with the Integration's Client Secret, deduplicates by Request-ID, and normalizes events to issue.created or event_alert.triggered.GitLabGitLab project webhooks cover pushes, merge requests, pipelines, issues, notes, and releases.HubSpotHubSpot CRM webhooks report contact, company, deal, and ticket creation and property changes.ShopifyShopify app webhooks send topic-scoped events such as orders/create, products/update, and refunds/create.IntercomIntercom sends conversation and contact notification topics, signed with the app client secret.ZendeskZendesk webhooks cover ticket, user, and organization events, signed with a timestamp plus body HMAC.NotionNotion webhooks report page, database, data source, and comment changes inside a workspace integration.JiraJira Cloud webhooks cover issue creation, updates, comments, and sprint changes.PagerDutyPagerDuty v3 webhooks cover incident trigger, acknowledge, resolve, and annotation events.Standard WebhooksStandard Webhooks deliveries carry webhook-id, webhook-timestamp, and base64 v1 signatures.SvixSvix Play and the Svix dispatcher use the Standard Webhooks headers with svix- prefixes.VercelVercel webhooks cover deployment, integration, project, and domain events.TwilioTwilio status callbacks cover messages, calls, and recordings, signed over the URL and form parameters.DiscordDiscord interaction webhooks use Ed25519 signatures plus a PING handshake.Generic HMACGeneric sources sign timestamp.deliveryId.body with HMAC-SHA256 and send the signature in x-signature.BitbucketBitbucket Cloud repository webhooks cover pushes, pull request changes, and issue events.TypeformTypeform webhook deliveries report form responses with the form id, response token, and submitted answers.CalendlyCalendly webhook deliveries report scheduled-event invitee bookings, cancellations, and no-shows.ResendResend email webhooks report sent, delivered, delayed, bounced, complained, opened, and clicked messages.ClerkClerk user-lifecycle webhooks report users, sessions, organizations and memberships as they are created, updated, or removed.CloudflareCloudflare Alerts webhooks deliver platform notifications such as health-check, load-balancing, WAF, Workers and billing alerts to a generic webhook destination.PolarPolar billing webhooks report checkout, order, subscription, customer and benefit-grant events for digital products.Lemon SqueezyLemon Squeezy webhooks report orders, subscriptions, subscription payments, license keys and affiliates for digital products.PaddlePaddle Billing webhooks report subscription, transaction, customer, adjustment and payout events for SaaS billing.SupabaseSupabase database webhooks report table inserts, updates and deletes, while Auth HTTP hooks send signed user lifecycle payloads.PostHogPostHog webhook destinations forward product analytics events and person properties to any HTTP endpoint.Azure DevOpsAzure DevOps service hooks send git pushes, pull requests, work items, builds and releases to a public webhook endpoint.ZoomZoom webhooks cover meeting, webinar, recording and user events, with a URL-validation handshake during app setup.Fireflies.aiFireflies.ai Webhooks V2 report meeting transcription, summary, and bot-join events for a transcript id.Recall.aiRecall.ai sends bot lifecycle webhooks (joining, recording, done, fatal) through Svix with Standard Webhooks signatures.Auth0Auth0 custom log streams POST tenant log events (login, signup, logout, token exchange, user changes) to a webhook.StytchStytch project webhooks cover user, session, organization, member, SAML/OIDC and SCIM changes, delivered through Svix.AsanaAsana webhooks cover task, project, section, story, team and goal changes, established by a one-time X-Hook-Secret handshake.ClickUpClickUp webhooks cover task, list, folder, space and goal changes, signed with a per-webhook secret over the raw body.monday.commonday.com webhooks cover item, column, subitem and update changes; app webhooks carry a JWT in Authorization.SquareSquare webhooks cover payments, refunds, orders, invoices and catalog changes, signed with the subscription's signature key over the notification URL and body.PayPalPayPal webhooks cover payment, sale, capture, refund, subscription and invoice events, signed with an RSA certificate that can be verified locally.GrafanaGrafana Alerting webhooks deliver firing and resolved alert groups, optionally signed natively with HMAC-SHA256.AirtableAirtable webhooks notify you when records in a watched table change; the changed records are fetched separately from the webhook payloads API.Cal.comCal.com booking webhooks wrap the booking in a triggerEvent envelope and sign each delivery with an HMAC-SHA256 of the raw body.AWS SNSAWS SNS delivers JSON notifications and subscription confirmations to HTTP(S) endpoints, signed with an RSA certificate published under an sns.<region>.amazonaws.com URL.PlanetScalePlanetScale organization webhooks cover branch, deploy request, backup, storage and maintenance events.ElevenLabsElevenLabs webhooks report post-call transcriptions, voice removals and image/video generation completions.