Stripe ➔ Supabase Webhook Pipeline Specification Webhook Specification, Headers & Security

Technical Integration Summary

Comprehensive specification for handling incoming Stripe ➔ Supabase Webhook Pipeline Specification webhook events. This reference covers cryptographic payload verification, request headers, and retry protocols.

Supported Events: charge.succeeded payment_intent.created invoice.payment_failed customer.subscription.deleted

Authentication & Request Headers

Security validation specs for Stripe ➔ Supabase Webhook Pipeline Specification endpoints:

Authorization: Bearer sec_live_b4bb5ec44174d45d

Signature Verification Implementations

Node.js (Express)

const crypto = require('crypto');
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
const isValid = crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature));

Python (Flask / FastAPI)

import hmac, hashlib
expected = hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
is_valid = hmac.compare_digest(expected, incoming_sig)

Sample Event Payload (charge.succeeded)

{
  "id": "evt_stripe-to-supabase.html_99265",
  "event": "charge.succeeded",
  "created_at": 1789764056,
  "data": {
    "resource_id": "res_304",
    "status": "active"
  }
}

cURL Request Simulation

curl -X POST https://your-domain.com/webhook/stripe-to-supabase.html \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer sec_live_b4bb5ec44174d45d" \
  -d '{"id": "evt_stripe-to-supabase.html_99265", "event": "charge.succeeded", "created_at": 1789764056, "data": {"resource_id": "res_304", "status": "active"}}'

HTTP Response Rules

Status Code	Status Meaning	Integration Action
`200 OK`	Success	Event payload validated and queued.
`400 Bad Request`	Malformed Payload	Check payload structure and JSON formatting.
`401 Unauthorized`	Signature Mismatch	Verify secret key and digest computation.
`500 Error`	Server Error	Triggers provider automated retry backoff.

Security Best Practices for Stripe ➔ Supabase Webhook Pipeline Specification

Always process incoming events asynchronously using a message queue. Never perform long-running DB queries or external API calls synchronously within the HTTP response handler.

Frequently Asked Questions

How to verify Stripe ➔ Supabase Webhook Pipeline Specification webhook authenticity?

Compute the HMAC SHA-256 hash on the raw request body using your shared secret and compare it against the incoming signature header using time-constant comparison.

Should I restrict incoming IP addresses for Stripe ➔ Supabase Webhook Pipeline Specification?

While signature verification is primary, restricting traffic to published origin IP ranges adds a robust layer of perimeter security.

How to handle duplicate Stripe ➔ Supabase Webhook Pipeline Specification webhooks?

Store processed event IDs in an atomic storage like Redis with a set expiration. If an incoming ID exists, acknowledge with 200 OK immediately without re-triggering logic.