billinglisted

# Stripe Billing (subscriptions, invoicing, metering) Recurring revenue on Stripe. This skill covers the **Billing** product family: Products & Prices, the Subscription lifecycle, trials, proration, cancellation, automated Invoicing, usage-based/metered billing, dunning/Smart Retries, the Customer Portal, and subscription-level tax. **Pinned Stripe API version: `2026-06-24.dahlia`.** The cross-cutting rules — key types & auth, idempotency, money/amount model, error taxonomy, Stripe CLI, test cards — are **not repeated here**; they live in the router **stripe-suite:integration** (`../integration/reference/foundations.md`, `../integration/reference/stripe-cli.md`, `../integration/reference/testing.md`). Every write below still needs an `Idempotency-Key`, a server-side secret/restricted key, and amounts as integers in the smallest currency unit. All examples are SDK-neutral (raw REST + a one-line cross-SDK note). Nothing here is framework-specific. --- ## When to use / decision tree You are in the right skill if the ask is about recurring charges. Three decisions shape the integration: ### Decision 1 — Fixed-price vs usage-based | The customer is billed… | Pricing model | Route | |---|---|---| | A fixed amount per interval (per seat, per plan, flat) | `billing_scheme=per_unit`, `recurring.usage_type=licensed` | `reference/prices-and-products.md` | | By what they consume (API calls, GB, events) | metered Price + **Billing Meters** (report `meter_events`) | `reference/usag