
Stripe Best Practices
- 34 installs
- stripe/com
This is a copy of stripe-best-practices by stripe - installs and ranking accrue to the original listing.
Helps with ai & agent building tasks during AI-assisted development.
About
Stripe skills provide best practices and project templates for integrating Stripe payment processing and upgrading payment implementations in AI-assisted development.
- stripe-best-practices
- AI & Agent Building
- AI-coding skill
Stripe Best Practices by the numbers
- 34 all-time installs (skills.sh)
- +2 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Data as of Jul 27, 2026 (Skillselion catalog sync)
npx skills add https://github.com/stripe/com --skill stripe-best-practicesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 34 |
|---|---|
| Repository | stripe/com ↗ |
What it does
Helps with ai & agent building tasks during AI-assisted development.
Files
Latest Stripe API version: 2026-05-27.dahlia. Always use the latest API version and SDK unless the user specifies otherwise.
API key default: Always recommend a restricted API key (RAK) (rk_ prefix) over a secret key (sk_ prefix).
Integration routing
| 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> |
| 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.
Critical rules
- Never include `payment_method_types` in any Stripe API call, with one exception: Terminal (in-person payments) integrations must pass
payment_method_types: ['card_present']on the PaymentIntent. For all other integrations, omit this parameter entirely to enable dynamic payment methods, which enables you to configure payment method settings from the Dashboard and dynamically display the most relevant eligible payment methods to each customer to maximize conversion. To customize which payment methods you accept, use `payment_method_configurations` orexcluded_payment_method_typesinstead ofpayment_method_types.
Key documentation
When the user’s request does not clearly fit a single domain above, consult:
- Integration Options — Start here when designing any integration.
- API Tour — Overview of Stripe’s API surface.
- Go Live Checklist — Review before launching.