Stripe Webhook Forwarding & Payment Pipeline

The Problem with a Single Webhook Handler

Stripe sends each payment event to one URL. If that URL is your fulfillment service, your Slack notifications never fire. If it's a Zapier zap, you're paying per event and adding latency. And if the downstream service is slow, Stripe sees a timeout and retries — potentially triggering your fulfillment twice.

Requex receives the event instantly, returns 200 to Stripe, then fires-and-forgets to each destination in parallel with configurable retries per rule.

Architecture

Step-by-Step Setup

1. 1

   Create a Requex endpoint

   Open requex.me and copy your unique webhook URL. No account needed — it's active immediately.

2. 2

   Enable HMAC auth

   In Settings → Auth, choose HMAC. Set the algorithm to sha256, the header name to Stripe-Signature, and paste your Stripe webhook signing secret as the secret value. Requex will reject any request that doesn't carry a valid signature.

3. 3

   Add forwarding rules

   Settings → Forwarding → Add Rule. Create one rule per destination. Enable "Pass-through body" and "Pass-through headers" so each service receives the original Stripe payload and headers intact.

4. 4

   Register in Stripe Dashboard

   Stripe Dashboard → Developers → Webhooks → Add endpoint. Paste your Requex URL. Select events: payment_intent.succeeded, payment_intent.payment_failed, checkout.session.completed.

5. 5

   Verify with Stripe test events

   In Stripe Dashboard, click "Send test webhook" → payment_intent.succeeded. Check the Requex request log — you'll see the payload and each forwarding rule's response under "Forwarding Logs".

Stripe Events Worth Forwarding