
Stripe Best Practices
This is opinionated routing guidance for Stripe integrations. It steers you toward Checkout Sessions for payments, Accounts v2 for Connect platforms, and restricted API keys by default. The integration routing table is the most useful bit: it maps what you're building to the right API surface before you start coding. There's a hard rule about never including payment_method_types (except for Terminal), which prevents a common mistake that locks you out of dynamic payment methods. Best used when you're starting a Stripe integration or reviewing code before it goes live, since it covers the current API version (2026-05-27.dahlia) and points to security, billing, and Treasury patterns.
- skills.sh installs
- 318
- GitHub stars
- 1.6K
- last updated
- Jun 3, 2026
Install
$ npx -y skills add stripe/agent-toolkit --skill stripe-best-practices --agent claude-codeInstalls into .claude/skills of the current project.
Files
Latest Stripe API version: 2026-10-28.endive. Always use the latest API version and SDK unless the user specifies otherwise.
Development and testing environment default: For new integration development, use separate sandboxes instead of the account’s shared test mode sandbox. Sandboxes isolate settings and test data from live mode. Use separate sandboxes for local development and CI. When stronger isolation is useful, dedicate sandboxes to development teams or testing scenarios. Use the shared test mode sandbox only for an existing integration that depends on it or when a required feature doesn’t support general sandboxes.
Latest SDK versions:
| Language | Latest version |
|---|---|
| Ruby | 20.0.0 |
| Python | 16.0.0 |
| Node.js | 23.0.0 |
| PHP | 22.0.0 |
| Java | 34.0.0 |
| Go | 87.0.0 |
| .NET | 53.0.0 |
Sponsors
Details
- Repository
- github.com/stripe/agent-toolkit
- Categories
- AI & Agent Building, Finance & Trading
- First seen
- Jun 3, 2026