Monetisation platform test-mode webhooks that never arrive in production

The newsletter for newsletter operators

Daily field notes on deliverability, AI tools, hosting, and monetisation. No "top 10 plugins" filler — real tools, real numbers, real failures.

Test-mode webhooks fire reliably. Your automation triggers on time. You flip the switch to production, and nothing happens.

The culprit is rarely a broken endpoint. Most monetisation platforms—Stripe, Gumroad, Lemon Squeezy, PayPal—handle test and live webhook configurations as separate entities, and some webhook events only exist in one mode. Others change payload structure or timing between environments. If you built your workflow against test data alone, you’ll discover the gaps when real money moves.

Test and live webhook endpoints are independent

When you configure a webhook URL in Stripe’s dashboard, you set it twice: once under Developers → Webhooks (Test mode) and again under Live mode. The URL can be identical, but the subscription is separate. If you only added the endpoint in test mode, live events won’t route to it (Stripe webhook docs, checked November 2026).

Gumroad follows the same pattern. Test-mode pings go to the URL you configure under Settings → Advanced → Webhooks when your account is in test mode, but switching to live mode requires re-saving the same URL or adding it again. The platform doesn’t auto-promote test configuration (Gumroad webhook guide, checked November 2026).

Lemon Squeezy uses a single webhook configuration that applies to both test and live transactions, but event payloads include a meta.test_mode boolean so your endpoint can branch logic. If you filter out test events server-side and forget to remove that filter before launch, live webhooks arrive but your handler ignores them (Lemon Squeezy webhook reference, checked November 2026).

Event types that only exist in production

Some webhook events require real-world conditions that test mode can’t replicate. Stripe’s radar.early_fraud_warning.created event fires when a card network flags a transaction for potential fraud—test cards never trigger this, because there’s no fraud signal to process. Chargeback events like charge.dispute.created can be manually triggered in test mode using the Stripe CLI, but the payload omits network reason codes and dispute evidence fields that only appear when a real bank initiates the claim.

PayPal’s PAYMENT.CAPTURE.REFUNDED webhook includes a seller_protection node in live mode when a refund qualifies for seller protection coverage. Test-mode refunds omit this node entirely, so if your automation parses it to decide whether to restock inventory, you’ll encounter a missing-key error the first time a live refund webhook arrives (PayPal webhook event reference, checked November 2026).

Timing differences between test and live

Stripe test-mode webhooks fire within seconds of the triggering event. Live-mode webhooks for subscription lifecycle events—customer.subscription.updated, invoice.payment_succeeded—can arrive minutes later when payment confirmation involves 3D Secure or bank network delays. If your workflow assumes webhooks arrive before the customer returns to your thank-you page, test mode won’t expose the race condition.

Gumroad test-mode sale webhooks arrive immediately after a test purchase. Live-mode sales that require payment review (fraud checks, unusual billing country) delay the webhook until Gumroad’s risk team approves the transaction, which can take hours. Your onboarding email might fire before access is granted, or not at all if you time out the webhook listener.

How to audit before you switch

Log every test-mode webhook your endpoint receives during a full purchase-to-refund cycle. Compare those event types against the platform’s live-mode event catalog—most providers publish a full list in their API docs. Look for events marked “live only” or notes about payload differences.

Run a small live transaction before you announce a product. Use a real card (your own, or a prepaid debit with a few dollars loaded) and complete the flow end-to-end. Refund immediately if needed. Check your webhook logs to confirm event types and payload structure match what your handler expects. Stripe and Lemon Squeezy both archive webhook delivery attempts in the dashboard, so you can inspect the exact JSON sent even if your endpoint returned an error.

For platforms that use separate test and live webhook URLs, set both to the same endpoint during the audit phase. Add a query parameter—?env=test vs. ?env=live—so your server logs can distinguish traffic sources. Once you’ve confirmed both environments behave identically, you can remove the test-mode subscription to reduce noise.

If your workflow depends on events that only fire in production (disputes, fraud warnings, failed recurring payments after multiple retry attempts), you can’t fully test them before launch. Document which events fall into this category, set up alerting so you’re notified when they arrive for the first time, and write error-handling code that logs the full payload and fails safely rather than silently skipping the event.

One thing to try this week: Open your payment processor’s dashboard, compare test-mode and live-mode webhook subscriptions, and confirm both point to the same endpoint. Then trigger one live transaction with a real card and verify the webhook arrives with the payload structure your code expects.

Got a workflow question? Reply to any One Two Three Send email—we read every one.

The newsletter for newsletter operators

Daily field notes on deliverability, AI tools, hosting, and monetisation. No "top 10 plugins" filler — real tools, real numbers, real failures.

Other newsletters you might like

Irish Rugby Fans

The best Irish rugby updates, straight to your inbox — Six Nations, the Nations Championship and the provinces. Only when there's something worth reading.

Subscribe

Love California

Love California — in your inbox The Pacific Coast Highway, national parks, beaches, wine country and the best places to visit in California. One short email, every day.

Subscribe

Springbokfans

The best Springbok updates, straight to your inbox. Only when something worth reading actually happens.

Subscribe

Love Spain

Love Spain — in your inbox. Iconic cities, hidden pueblos and the best places to visit in Spain. One short email, every day.

Subscribe

Newsletters via the One Two Three Send network.  ·  Want your newsletter featured here? Click here