Promos

Every coupon, newest first. `include_deleted` adds the ones already deleted at Stripe — their rows are kept so past redemptions still resolve to the terms that were granted.

Create the discount's terms. The console names the plans it applies to (`applies_to_plan_names`, from `GET /promos/plans`); payments resolves each to the active plan's Stripe Product, which is why a name that is not an active priced plan comes back as a 400 rather than a silent unrestricted coupon. The restriction is immutable afterwards — a different set of plans is a different coupon.

`idempotency_key` is the console's, generated once per form submission and passed to Stripe verbatim, so a retry after a lost response returns the first coupon instead of minting a second.

The detail screen: the coupon plus its code strings, each with its allowlist. A targeted code is issued once per business under the same string, so the entries **are** the allowlist; a public code has a single entry with no business. Every entry's business is enriched with its `company_name` here — payments stores only ids.

Delete at Stripe. New redemptions stop and every code under it goes inactive, but **discounts already granted keep running to their duration** — Stripe copies the terms onto the subscription at redemption, so deleting the coupon does not claw anything back. The mirror row survives, flagged deleted, so past redemptions still name their terms.

No `businesses` mints one public code; with them, one customer-restricted code **per business** sharing the string — which is also how a business is added to an existing code's allowlist.

Unknown businesses are refused here, before payments is called: payments would create a Stripe Customer for the id to restrict the code to, and a Customer minted for a typo is permanent. The `company_name` sor holds is passed along to label that Customer, because payments has no other source for it.

The plan picker on the coupon form. This is payments' catalogue **without** the free plan: a plan with no Stripe price has no Product to carry a discount, so offering it would only produce a 400 on submit. The names here are exactly what `applies_to_plan_names` takes.

`active=false` is how a business leaves an allowlist — codes are never deleted at Stripe. `listed_for_auto_apply` controls whether the catalogue advertises the code in the customer's promo dropdown; an unlisted code still works when typed at Checkout.

Stripe refuses to reactivate a code that expired, hit its cap, or whose coupon was deleted, and that refusal reaches the admin verbatim rather than as a generic failure.

Redemption reporting, newest first, filterable by business, coupon or code. A row is a Stripe Discount as payments mirrors it, so `ends_at` is null while the discount is still running. Each row's business is named here from sor's table.