stripe-webhook-auditor

Audit Stripe webhook event handling and identify missing handlers.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill stripe-webhook-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-webhook-auditor
Source: https://github.com/Sebdysart/omni-link-hustlexp/tree/main/skills/stripe-webhook-auditor
Command: npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill stripe-webhook-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and fix issues with Stripe webhook handling, particularly focusing on missing revenue logging, subscription renewal gaps, payout failures, and ensuring complete webhook event coverage.

Core Features & Use Cases

  • Webhook Architecture Analysis: Understand the flow from Stripe to your backend, including verification, storage, and dispatch.
  • Identify Missing Handlers: Pinpoint which Stripe events are not being processed, leading to silent failures or lost data (e.g., invoice.payment_succeeded).
  • Implement Fixes: Provides step-by-step guidance and code examples to add missing webhook handlers and ensure revenue is logged correctly.
  • Idempotency Assurance: Explains HustleXP's two-layer idempotency system to prevent duplicate processing.
  • Use Case: If your subscription revenue reports are showing gaps after the first month, this Skill will guide you to identify that invoice.payment_succeeded is not wired and show you how to fix it.

Quick Start

Use the stripe-webhook-auditor skill to audit all currently handled Stripe event types in the backend jobs worker.

Frequently Asked Questions about stripe-webhook-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are my Stripe subscription renewals not logging revenue after the first month?

Stripe webhook auditing identifies missing event handlers causing silent revenue failures. It traces webhook flow from verification to dispatch, pinpointing unhandled events like `invoice.payment_succeeded` that prevent subscription renewals from logging correctly.

How do I audit which Stripe webhook events are missing handlers in my backend?

Stripe webhook auditing maps your backend's event handling coverage against expected subscription lifecycle events. It identifies unprocessed event types and provides code snippets to wire missing handlers into your event worker.

What is the best way to ensure idempotency when processing Stripe webhook events?

Stripe webhook idempotency requires a two-layer system spanning ingestion and processing. This prevents duplicate revenue logging or subscription updates when Stripe retries webhook delivery to your backend.

How do I fix Stripe payout failures and missing subscription lifecycle events?

Stripe webhook auditing diagnoses payout failures and subscription lifecycle gaps by analyzing your backend architecture. It provides implementation steps to add missing event handlers and ensure complete revenue logging coverage.

Can I use this webhook auditor if my backend does not use a separate jobs worker?

Stripe webhook auditing is designed for backends with a dedicated jobs worker like `stripe-event-worker.ts`. If your architecture handles webhooks synchronously, the architectural diagrams and handler patterns still apply but require adaptation.