
Cuts through Stripe's overwhelming API surface by routing you to the right integration path upfront. Instead of guessing between PaymentIntents and Checkout Sessions, or wondering which Connect API version to use, it gives you a decision matrix based on what you're actually building. Covers the tricky stuff like migrating off deprecated APIs, setting up restricted API keys properly, and navigating Connect's liability models. The routing table alone saves hours of documentation diving. Honestly wish this existed when I was first wrestling with Stripe's marketplace setup, would have prevented a lot of refactoring.
$ npx -y skills add stripe/ai --skill stripe-best-practices --agent claude-codeInstalls into .claude/skills of the current project.
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