84 /100
Strong for local payment testing when limited to test mode and webhook workflows.
Structured output 86/100
Whether the CLI can return JSON, YAML, or stable machine-readable output.
Non-interactive use 82/100
Whether common workflows can run predictably without an interactive prompt.
Safety boundaries 66/100
Whether read-only, dry-run, scoped auth, and destructive command boundaries are clear.
Install options
Homebrew
$ brew install stripe/stripe-cli/stripe Docker
$ docker run --rm -it stripe/stripe-cli Common commands
Listen for webhooks · safe
$ stripe listen --forward-to localhost:3000/api/webhooks/stripe Forwards test webhooks to local development.
Trigger checkout event · safe
$ stripe trigger checkout.session.completed Creates a test event for webhook validation.
Create live refund · destructive
$ stripe refunds create --charge ch_... Moves money and must not be agent-autonomous.
Agent usage examples
Claude Code
Use Stripe CLI in test mode to trigger webhook events and verify handlers. Never run live refund or cancellation commands without approval. Safety notes
- Listen and trigger commands are good for local webhook testing.
- Commands that create, refund, or cancel live resources must require explicit approval.
- Use test mode keys for agent-driven development work.
TL;DR
Stripe CLI is strong for local payment development when the agent is restricted to test mode, webhook forwarding, and fixture events.
Agent-safe workflow
- Confirm the project is using test keys.
- Forward test webhooks with
stripe listen --forward-to localhost:3000/api/webhooks/stripe. - Trigger representative test events such as
checkout.session.completed. - Inspect local server logs and webhook handler output.
- Summarize which event types passed, failed, or were not handled.
Requires confirmation
Do not let the agent create live refunds, cancel subscriptions, update live customers, or change account-level settings without explicit user confirmation.