Supabase Stripe Webhook Tutorial: Subscriptions Sync
This Supabase Stripe webhook tutorial builds production billing sync: checkout edge function, signature-verified webhook handler with idempotency, and webhooks vs the Stripe Sync Engine.
<!-- BRIEF SPEC (not published): Variant: DEEP-GUIDE | Hook: PROBLEM-AGITATION | FAQ: 8 | Cover: DARK-NEON (navy/black, teal+amber glow, 3D credit-card/webhook-bolt shape — distinct accents from the embeddings cover) In-body images: (1) Sequence diagram: Stripe -> webhook endpoint -> edge function -> Postgres subscriptions table -> Flutter app. (2) Screenshot-style mock of the Stripe dashboard webhook endpoint page with events selected. SERP structure notes (structure only): top results are GitHub README setup guides — strong on dashboard steps and event lists, weak on failure modes (signature bugs, retry storms, idempotency) and on the Sync Engine comparison. Gap we exploit: production failure modes + head-to-head verdict + Dart/Flutter context. Verified versions: Flutter 3.47.6 / Dart 3.13.5, @supabase/supabase-js 2.117.2, supabase_flutter 2.x stable. Stripe SDK unpinned (npm:stripe) — no invented version. --> Last updated: 2026-10-10 A customer pays. Stripe fires the webhook. Your edge function throws on a signature check, returns a 500, and Stripe retries for three days before giving up. Meanwhile your app still shows that paying customer the free plan — and support tickets start arriving. This is the failure mode every Stripe billing tutorial skips: getting money into Stripe is the easy part; keeping your Postgres in sync with Stripe, through retries, out-of-order events, and signature quirks, is the actual engineering. This Supabase Stripe webhook tutorial builds the whole thing the production way — then compares it honestly against the Stripe Sync Engine so you can pick the right tool. What you'll build A subscriptions table that mirrors Stripe state per user, with RLS A create-checkout edge function that starts Stripe Checkout sessions A stripe-webhook edge…