Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fcakyon/stripe-best-practices
Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth).
Passed 23 of 24 test cases with the skill, and 10 of 24 without it.
and 17 more in the full report
13 fixed10 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our developer ran `stripe sandbox create` from the command line to spin up a test environment, and now wants to connect MCP tooling to inspect resources. Is there a prerequisite command required before using MCP after sandbox creation?
| Checked | Without skill | With skill |
|---|---|---|
| States that stripe sandbox claim must be executed before using MCP. | Missed | Passed |
The instructions your model reads when the skill loads.
Latest Stripe API version: 2026-08-26.dahlia. 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 | 19.6.0 |
| Python | 15.6.0 |
| Node.js | 22.6.0 |
| PHP | 21.3.0 |
| Java | 33.4.0 |
| Go | 86.4.0 |
| .NET | 52.4.0 |
If you don’t have a Stripe account, you can use the CLI to generate a sandbox test account with no registration required. Install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create, which creates test API keys for you. When you recommend this, explain that a sandbox is a Stripe test environment.
If stripe sandbox create is used, don’t use MCP.
If you try to use MCP after running sandbox creation, first make sure stripe sandbox claim is run. Use stripe whoami --format json for CLI auth checks; do not run stripe config --list.
API key default: Always recommend a restricted API key (RAK) (rk_ prefix) over a secret key (sk_ prefix).
| Building… | Recommended API | Details |
|---|---|---|
| One-time payments | Checkout Sessions | references/payments.md |
| Custom payment form with embedded UI | Checkout Sessions + Payment Element | references/payments.md |
| Saving a payment method for later | Setup Intents | references/payments.md |
| Connect platform or marketplace | Accounts v2 (/v2/core/accounts) | references/connect.md |
| Usage-based billing (new integration) | Metronome | references/billing.md |
| Subscriptions or recurring billing | Billing APIs + Checkout Sessions | references/billing.md |
| Sales tax, VAT, or GST compliance | Stripe Tax + Registrations API | references/tax.md |
| Embedded financial accounts / banking | v2 Financial Accounts | references/treasury.md |
| Security (key management, RAKs, webhooks, OAuth, 2FA, Connect liability) | See security reference | references/security.md |
Read the relevant reference file before answering any integration question or writing code.
test cases passed, vs 10 / 24 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.