Stripe CLI Logs, Config, and Troubleshooting

Profiles, config, request logs, diagnostics, and troubleshooting patterns for the Stripe CLI.

View
StandardDetailedCompact
Export
Copy the compact sheet, download it, or print it.
Download
`D` dense toggle · `C` copy all
## Profiles and Config
List current config
stripe config --list
Show config help
stripe config --help
Run with a named profile
stripe logs tail --profile sandbox-a
Use STRIPE_API_KEY from the environment
STRIPE_API_KEY=sk_test_xxx stripe customers list --limit 3

# Run a command using the environment-provided key instead of interactive login.

Persist local project webhook secret example
echo "STRIPE_WEBHOOK_SECRET=whsec_xxx" >> .env.local
## Logs and Observability
Tail request logs
stripe logs tail
Tail live-mode request logs
stripe logs tail --live
Show only request failures with jq
stripe logs tail | jq "select(.status >= 400)"
Inspect recent pending webhook events
stripe events list --limit 100 | jq ".data[] | select(.pending_webhooks > 0) | {id, type, pending_webhooks}"
Save a log stream to a file
stripe logs tail > stripe-request-log.jsonl
## Troubleshooting Patterns
Inspect a failing command with --help
stripe payment_intents create --help
Verify the listen output includes a signing secret
stripe listen --forward-to localhost:3000/api/webhooks/stripe

# When local webhook signature checks fail, restart listen and copy the current whsec value.

Expand related objects to debug missing fields
stripe checkout sessions retrieve cs_test_123 --expand payment_intent --expand customer
Retry a request on latest API version
stripe customers create --email ada@example.com --latest
Export past-due subscriptions to CSV with jq
stripe subscriptions list --status past_due --expand data.customer | jq -r ".data[] | [.customer.name, .customer.email] | @csv"

Recommended next

No recommendations yet.