How to Test Stripe Webhooks: Complete Guide

Why Stripe Webhook Testing is Critical

Stripe webhooks are the backbone of payment processing. Every time a payment succeeds, a subscription renews, a dispute is opened, or a payout is sent, Stripe fires a webhook event. If your application doesn't correctly handle these events, you risk missing payments, granting unauthorized access, or failing to fulfill orders.

Unlike API calls where you get an immediate response, Stripe webhooks are asynchronous. A customer may complete a checkout session, but your server might not process the checkout.session.completed event for several seconds. If that webhook fails silently, the customer's order may never be fulfilled — even though they were charged.

This guide walks you through testing every critical Stripe webhook event, from basic payment intents to complex subscription lifecycle management.

Key Stripe Webhook Events You Must Handle

Method 1: Test with Requex.me (Fastest)

The quickest way to understand Stripe webhook payloads is to capture them with Requex.me:

1. Visit requex.me and copy your unique webhook URL.
2. Go to Stripe Dashboard → Developers → Webhooks → Add Endpoint.
3. Paste your Requex URL, select the events you want to test, and click "Add endpoint".
4. Click "Send test webhook" in Stripe's dashboard for any event type.
5. Watch the payload appear instantly in your Requex dashboard.

This lets you inspect the exact JSON structure Stripe sends, including nested objects, metadata, and edge-case fields that documentation often misses.

Method 2: Stripe CLI for Local Testing

The Stripe CLI provides direct forwarding to your local server:

# Install Stripe CLI
brew install stripe/stripe-cli/stripe

# Login to your Stripe account
stripe login

# Forward events to your local server
stripe listen --forward-to localhost:3000/api/webhooks/stripe

# In another terminal, trigger test events:
stripe trigger payment_intent.succeeded
stripe trigger customer.subscription.created
stripe trigger invoice.payment_failed

The CLI provides a temporary webhook signing secret (displayed when you run stripe listen). Use this secret in your local environment for signature verification.

Stripe Webhook Signature Verification

Stripe signs every webhook with your endpoint's signing secret. Always verify this signature in production:

// Node.js / Express example
const stripe = require('stripe')('sk_test_...');

app.post('/api/webhooks/stripe', express.raw({type: 'application/json'}), (req, res) => {
  const sig = req.headers['stripe-signature'];
  const endpointSecret = process.env.STRIPE_WEBHOOK_SECRET;
  
  let event;
  try {
    event = stripe.webhooks.constructEvent(req.body, sig, endpointSecret);
  } catch (err) {
    console.log('Webhook signature verification failed:', err.message);
    return res.status(400).send('Webhook Error');
  }

  // Handle the event
  switch (event.type) {
    case 'payment_intent.succeeded':
      const paymentIntent = event.data.object;
      // Fulfill the order...
      break;
    case 'payment_intent.payment_failed':
      // Notify the customer...
      break;
    default:
      console.log('Unhandled event type:', event.type);
  }

  res.status(200).json({received: true});
});

Common Stripe Webhook Issues

Testing Checklist for Stripe Webhooks