Stripe
Header Stripe-Signature with timestamp t and HMAC-SHA256 v1 over {timestamp}.{raw_body}.
- Read the raw body before JSON parse.
- Extract
tandv1. - HMAC with
whsec_.... - Constant-time compare.
- Reject stale timestamps (replay window).
Stripe, GitHub, and Slack all sign webhook payloads with HMAC-SHA256. You can test verification in your browser, so your signing secret stays on your device.
When a signature check fails, it is tempting to paste the signing secret into the first “online HMAC” site you find. This guide explains how each provider builds its signature, then shows how to reproduce the header privately with the Webhook HMAC Signer. The most common cause of a mismatch is verifying a parsed and re-serialized body instead of the exact raw bytes the provider sent. Our blog post on verifying webhook signatures locally covers more debugging cases.
Header Stripe-Signature with timestamp t and HMAC-SHA256 v1 over {timestamp}.{raw_body}.
t and v1.whsec_....Header X-Hub-Signature-256 as sha256= plus hex HMAC-SHA256 of the raw body.
Header X-Slack-Signature from base string v0:{timestamp}:{raw_body}, HMAC-SHA256, prefixed v0=.
X-Slack-Request-Timestamp.Choose Stripe, GitHub, or Slack so the tool builds that provider’s signed string.
Everything stays in the tab. Use a test-mode secret rather than a production one whenever you can.
Build the expected header, or check an incoming header against the payload.
Need a sample payload to sign? Generate one with the Webhook Payload Simulator. To see why a retried delivery behaves differently, compare two deliveries in the Webhook Replay Diff Lab. If you need a record of the check, download a privacy receipt after the job.