---
name: Stripe CLI
slug: stripe-cli
url: https://docs.stripe.com/webhooks
category: Payments
bestFor: "Forwarding Stripe webhook events to a local server so you can test signature verification."
freeTier: yes
price: "Not stated"
checks: []
freeTierNote: "Stripe's webhook documentation tells you to install the Stripe CLI and run `stripe listen --forward-to` when you do not yet have a public HTTPS URL. The command prints a webhook signing secret for those forwarded events. The page does not list a separate price for the CLI."
verifiedOn: "2026-10-13"
sources:
  - https://docs.stripe.com/webhooks
unknowns:
  - "A dedicated CLI pricing page was not fetched. This entry only says the webhook guide presents the CLI as the local testing tool and does not show a CLI charge."
---

The CLI is how you test the bug in [unverified Stripe webhooks](/issues/unverified-stripe-webhooks) without deploying. `stripe listen` gives you a signing secret that matches the events it forwards. The secret in the Dashboard is for the deployed endpoint. They are different.

The CLI does not make the handler safe. You still have to verify the signature and ignore the body when verification fails.