Strong for local payment testing when limited to test mode and webhook workflows.
Whether the CLI can return JSON, YAML, or stable machine-readable output.
Whether common workflows can run predictably without an interactive prompt.
Whether read-only, dry-run, scoped auth, and destructive command boundaries are clear.
Install options
$ brew install stripe/stripe-cli/stripe $ docker run --rm -it stripe/stripe-cli Common commands
$ stripe listen --forward-to localhost:3000/api/webhooks/stripe Forwards test webhooks to local development.
$ stripe trigger checkout.session.completed Creates a test event for webhook validation.
$ stripe refunds create --charge ch_... Moves money and must not be agent-autonomous.
Agent usage examples
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
1. Confirm the project is using test keys. 2. Forward test webhooks with `stripe listen --forward-to localhost:3000/api/webhooks/stripe`. 3. Trigger representative test events such as `checkout.session.completed`. 4. Inspect local server logs and webhook handler output. 5. 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.