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.