stripe-integration

Topics in the source

• Stripe Integration
• Versions
• Choose the API
• Rules
• Fulfill from webhooks, never from the success page
• Verify every webhook signature on the raw body
• Use idempotency keys on every create
• Let Stripe pick payment methods

Guidance for building payment code that does not lose orders, double-charge or leak keys. It follows Stripe's own recommendations as of October 2026. When a detail matters (a parameter, an event name, an API version), check docs.stripe.com or the Stripe MCP server's searchstripedocumentation tool before relying on memory. Latest API version: 2026-09-30.endive. Pin it explicitly on the client so an account default change never alters response shapes under you. Latest server SDKs: Node.js 23, Python 16, Ruby 20, PHP 22, Java 34, Go 87, .NET 53. Create a client instance; the global key pattern (stripe.apikey = …, Stripe.setApiKey) is deprecated in every SDK. To move an existing integration to a newer version, read Upgrading your API version first. | Building | Use | |---|---| | One-time payment, simple product | Payment Links (no code) or Checkout Sessions | | One-time payment in your web app | Checkout Sessions (hosted or embedded) | | Custom payment form | Checkout Sessions with uimode: 'custom' + Payment Element | | Save a card for later | Setup Intents | | Charge off-session (no customer present) | Payment Intents with a saved payment method | | Subscriptions, seats, trials | Bill

This is an excerpt. Refer to the complete source and its current requirements.