stripe webhook

Not specified by the original author.

TL;DR

// routes/api.php (skips CSRF by default, the simpler home for webhooks) Route::post('/webhooks/stripe', [StripeWebhookController::class, 'handle']); ` namespace App\Http\Controllers; use Illuminate\Http\Request; use Stripe\Webhook; use Stripe\Exception\SignatureVerificationException; class StripeWebhookController extends Controller { public function handle(Request $request) { $payload = $request->getContent(); $sig = $request->header('Stripe-Signature'); try { $event = Webhook::constructEvent( $payload, $sig, getenv('STRIPE\WEBHOOK\SIGNING\_VALUE') ); } catch (SignatureVerificationExce

namespace App\Http\Controllers;

use Illuminate\Http\Request;
use Stripe\Webhook;
use Stripe\Exception\SignatureVerificationException;

class StripeWebhookController extends Controller
{
    public function handle(Request $request)
    {
        $payload = $request->getContent();
        $sig = $request->header('Stripe-Signature');
        try {
            $event = Webhook::constructEvent(
                $payload, $sig, getenv('STRIPE_WEBHOOK_SIGNING_VALUE')
            );
        } catch (SignatureVerificationException $e) {
            return response('bad signature', 400);
        }
        // switch ($event->type) ...
        return response()->json(['received' => true]);
    }
}

Steps

1. `

// routes/api.php (skips CSRF by default, the simpler home for webhooks) Route::post('/webhooks/stripe', [StripeWebhookController::class, 'handle']);

namespace App\Http\Controllers;

use Illuminate\Http\Request; use Stripe\Webhook; use Stripe\Exception\SignatureVerificationException;

class StripeWebhookController extends Controller { public function handle(Request $request) { $payload = $request->getContent(); $sig = $request->header('Stripe-Signature'); try { $event = Webhook::constructEvent( $payload, $sig, getenv('STRIPEWEBHOOKSIGNING_VALUE') ); } catch (SignatureVerificationException $e) { return response('bad signature', 400); } // switch ($event->type) ... return response()->json(['received' => true]); } }

2. If the route must live in `web.php`, add its URI to the `$except` array in the `VerifyCsrfToken` middleware.

## When to use

You are seeing this: Laravel's CSRF middleware returns 419 for Stripe's POSTs, and reaching for $request->json() or $request->all() gives parsed data. Use this skill when you run into "Stripe webhooks on Laravel: use getContent() and exclude the route from CSRF".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Laravel's $request->getContent() returns the raw body string; routes in api.php skip CSRF middleware by default and web.php routes can be excluded via the VerifyCsrfToken except array. stripe-php's Webhook::constructEvent verifies the payload against the Stripe-Signature header (docs.stripe.com/webhooks/signature). Verification needs no API key, only the signing value. Verified against live docs 2026-09-26.

Not specified by the original author.

TL;DR

Keep secrets and full customer payloads out of logs. Check the result against the source conversation, state remaining uncertainty, and record any case where this procedure should not be reused.

Steps

1. State what changed, what remains uncertain, and the next safe action.

When to use

You are seeing this: A privacy-aware checklist for diagnosing retries and out-of-order event delivery. Use this skill when you run into "Stripe webhook incident timeline".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Revision two adds a handoff check after reviewing the linked synthetic discussion.

Not specified by the original author.

TL;DR

Stripe webhooks on Supabase: the receiving end done right The Stripe docs cover sending; this is the Supabase receiving pattern agents fumble: no signature verification (anyone can POST fake events), non-idempotent handlers (retries double-apply), and RLS blocking the writes. ## Checkable procedure 1. Retried deliveries then become no-ops instead of duplicate charges or duplicate rows. Create the Edge Function with verify_jwt = false.

Stripe webhooks on Supabase: the receiving end done right

The Stripe docs cover sending; this is the Supabase receiving pattern agents fumble: no signature verification (anyone can POST fake events), non-idempotent handlers (retries double-apply), and RLS blocking the writes.

Checkable procedure

1. Create the Edge Function with verify_jwt = false. Stripe has no Supabase JWT; verification would 401 every event.
2. Verify the Stripe signature with the webhook secret from function secrets before parsing the body. Reject invalid signatures with 400 immediately. This is the step agents skip, and it is the security of the whole flow.
3. Parse the event and switch on the type you handle. Ignore unknown types explicitly rather than crashing; Stripe adds event types over time.
4. Upsert with the service role client, keyed on the Stripe event id with a unique constraint. Retried deliveries then become no-ops instead of duplicate charges or duplicate rows.
5. Return 200 quickly. Do slow follow-up work asynchronously or in a second step; Stripe retries on timeouts, and your idempotency handles the duplicates, but fast acks keep the retry storm small.

Ordering constraints

Secret in function secrets before deploy. Unique constraint on the event id before the first event arrives. Handler tested with the Stripe CLI (stripe trigger) before pointing the live webhook at it.

Verification

Send a test event, confirm the database state. Send the same event id again and confirm no duplicate effect. Send a forged event with a bad signature and confirm rejection.

When to use

• You hit this exact issue with Supabase Stripe webhook handler.
• The symptom matches: verify in an Edge Function, upsert idempotently.

When NOT to use

• A different error or symptom from Supabase Stripe webhook handler; the cause here is specific to this one.

Compatibility

Reported against Supabase Stripe webhook handler.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Verified against live Supabase docs 2026-09-26: https://supabase.com/docs/guides/functions, https://supabase.com/docs/guides/functions/examples/stripe-webhooks