Stripe billing

Stripe holds the money. Your database holds the entitlement. Every serious billing defect is one fact living in two systems that stopped agreeing — a price, a quantity, a period, a refunded total.

Stripe's API is not where integrations fail. Failures happen at the seam: the callback that arrived twice, the renewal that granted a month of product for a $0.40 proration invoice, the upgrade that charged the card and then failed to write the row.

This skill is that seam. For which Stripe primitive to use (Checkout vs PaymentIntents, Connect, Tax, usage-based billing) the official stripe-best-practices skill is the authority and wins any disagreement; for lookups, stripe-docs. Examples are TypeScript; the rules are language-neutral.

Deep material, loaded on demand: