Catalog And Checkout Defaults
Pack:
stripeParent skill: Stripe Checkout And Pricing Model Defaults Source:stripe/stripe-checkout-and-pricing-model-defaults/references/catalog-and-checkout-defaults.mdCatalog default:
- Product = what the customer is buying
- Price = how much and how often Stripe charges
- lookup key = stable app-facing handle when you need indirection
Default pricing path:
- Start with flat-rate or per-seat pricing if either can express the business cleanly.
- Add usage-based pricing only when the business model really depends on measured usage.
- Keep the first catalog small.
Checkout default:
- Use hosted Checkout Sessions.
- Create sessions on the server.
- Pass existing price IDs.
- Use metadata and client reference IDs only for reconciliation, not authorization.
- Use webhooks for fulfillment.
Good reasons to stay hosted:
- lower implementation complexity
- built-in payment method support
- easier tax and promotion support
- less UI maintenance
Good reasons to deviate:
- your product needs a deeply embedded custom flow
- the UI constraints are not acceptable
- the business logic truly requires a custom payment collection experience