Stripe CLI listen silently drops webhook events when local SDK uses a different API version
When a developer runs `stripe listen` to forward webhooks locally, the CLI filters out events whose API version does not match the account default. If the developer is using a third-party package that pins an older Stripe API version, or is testing against a specific pinned version, the CLI silently drops the event with `Received event with non-default API version, ignoring`. There is also no `--stripe-version` flag on the `listen` command to override this. As of June 2026 the issue is still open with 43 reactions. Developers working with multi-version codebases, legacy integrations, or pinned-version OSS packages have no way to test webhooks locally against the version they actually ship. A CLI proxy or lightweight tool that intercepts the Stripe event stream and re-emits it at the version the developer specifies would close this gap.
Score Breakdown
Social Proof 2 sources
Gap Assessment
Two open GitHub issues: #1335 (43r+18c=61, last updated June 2026, no label, Stripe has not commented) and #600 (20r+45c=65, closed but without a real fix -- root cause persists). No third-party proxy tool found that solves the API version filter on `stripe listen`.