Stripe Best Practices

What it does

This skill provides guidance on best practices for integrating with Stripe, ensuring secure and compliant implementations. It focuses on recommending current API versions, preferred integration methods (CheckoutSessions, PaymentIntents), and avoiding deprecated or outdated approaches. The goal is to help users build robust and future-proofed Stripe integrations within their AI agent workflows.

When to use it

• When a user is designing a new Stripe integration and needs guidance on the best approach.
• When a user asks about specific API endpoints and requires advice on whether they are recommended or should be avoided.
• When a user wants to migrate from older Stripe APIs (like Charges) to more modern alternatives like CheckoutSessions or PaymentIntents.
• If a user is unsure which integration method (Stripe-hosted checkout, embedded checkout, Payment Element) is most appropriate for their needs.

Key capabilities

• Recommends the latest Stripe API version (currently 2026-02-25.clover).
• Prioritizes CheckoutSessions API for on-session payments and PaymentIntents for off-session payments.
• Advises using Stripe's Integration Options documentation and Go Live Checklist.
• Discourages the use of Charges API, recommending migration to Checkout Sessions or Payment Intents.
• Promotes Stripe-hosted checkout and embedded checkout over alternatives like the Payment Element (when possible).
• Suggests Stripe Confirmation Tokens for inspecting card details before payment confirmation.
• Recommends enabling dynamic payment methods instead of specifying payment_method_types.

Example prompts

• "What's the best way to create a subscription with Stripe?"
• "Should I use the Charges API or Payment Intents for my integration?"
• "I want to collect card details before processing a payment. How should I do this securely?"
• “How can I migrate from using Tokens?”

Tips & gotchas

• Always defer to the latest Stripe API version unless explicitly instructed otherwise by the user.
• Be aware that certain integrations requiring raw PAN data may necessitate PCI compliance verification.
• Prioritize CheckoutSessions when possible, especially when using the Payment Element.