The verified-event half of subscription access: one install covers the whole billing lifecycle, so a seller who has enrolled Stripe does not have to assemble it lane by lane. A subscription checkout completion reaches paid only through core.seller.order.confirm-payment after a fresh Session read, and only once a fresh invoice-payment read proves which PaymentIntent settled it — a subscription-mode Session exposes none. Renewal invoices are the second half: each paid subscription_cycle invoice becomes its own order for that billing period, confirmed only through core.seller.order.confirm-renewal-payment after fresh invoice, subscription, and invoice-payment reads, and the customer's access is extended from the order's own tier snapshot. billing_reason is the seam — subscription_create belongs to the checkout observer, subscription_cycle to the renewal flow, so the two never settle the same payment twice. Four further lanes keep access converged with the provider once it is selling: a failed invoice reports the subscription's confirmed status, a deleted subscription closes access, and a plan or entitlement change swaps the customer onto the tier their entitlements now say they hold. None of them decides what a status costs a customer — each reports provider-confirmed state and your status policy (Settings -> Seller) decides grace, immediate close, or keep active. The housekeeping reconciler remains the authority and converges all of it on its own sweep; these lanes only remove the wait. The order row is the single lifecycle record (Settings -> Seller -> Orders). Event snapshot fields are never transition authority. This pack sells nothing on its own: it observes payment for orders another flow opened, and it is deliberately independent of document fulfilment. It rides the bounded Stripe for Sellers surface, not the full API front door.