stripe-best-practices
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), 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, API key permissions, webhooks, OAuth). Use when planning, building, modifying, testing, or reviewing any Stripe integration, including choosing a development environment, accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.
- License
- MIT
- Pinned revision
- 1e24cf59cb0dd78df298afc3b7d372e5a5055ece
Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.
references/treasury.md
Treasury / Financial Accounts
Table of contents
- v2 Financial Accounts API
- Legacy v1 Treasury
v2 Financial Accounts API
For embedded financial accounts (bank accounts, account and routing numbers, money movement), use the v2 Financial Accounts API (POST /v2/core/vault/financial_accounts). This is required for new integrations.
For Treasury for platforms concepts and guides, see the Treasury for platforms overview.
Legacy v1 Treasury
Don’t use the v1 Treasury Financial Accounts API (POST /v1/treasury/financial_accounts) for new integrations. Existing v1 integrations continue to work.