With no Stripe key, the Products and Billing pages and the billing sweeps still act on Stripe objects an earlier key made #299

New Issue

2026-10-30T22:44:40Z

cgalo5758 commented

2026-10-30 22:44:40 +00:00

What happens

A deployment can run without a Stripe key. A price mapping, a subscription mapping and an invoice mapping are the console's records of the Stripe objects its prices, subscriptions and invoices were synced to; a deployment that once had a key keeps them after the key is removed. The question "can the current key reach this recorded Stripe id" answers yes when there is no key (MappingReachable, internal/integrations/stripe/store/mapping_environment.go:89), a rule written for a key the console cannot classify, which boot no longer accepts.

So on such a deployment, an organization whose subscription the earlier key sold sees Cancel plan, Keep plan, Resume plan and the downgrade to a held or free rung on the Products page, because those moves buy nothing and read no price, and the Billing page draws Pay on an open invoice. Each plan move reaches a Stripe call made with no key, or an outbox entry that cannot run, and the member reads a failure; Pay returns the member to the Billing page without saying why.

Background work asks the same question with no key: the sweep that applies scheduled plan changes (its schedule starts whatever the key), the invoice collection sweep and the reconcile's skip. The setup checklist's price step counts any recorded price mapping as done.

What should happen

With no Stripe key, no page offers a Stripe action and no background job attempts one, whatever mappings an earlier key left; the setup checklist does not count them. Whether the reach question answers no decides all of these, and what each page then shows needs deciding with it.

Where

internal/integrations/stripe/store/mapping_environment.go; internal/server/plan_offer.go, billing.go, member_invoices.go, member_hosted_invoice.go; internal/fulfillment/sweep.go, collection_sweep.go, reconcile.go, plan_change.go

Why it matters

A member on a deployment that removed its key is offered plan changes and payments that fail, and background jobs keep failing against Stripe with no key.

### What happens A deployment can run without a Stripe key. A price mapping, a subscription mapping and an invoice mapping are the console's records of the Stripe objects its prices, subscriptions and invoices were synced to; a deployment that once had a key keeps them after the key is removed. The question "can the current key reach this recorded Stripe id" answers yes when there is no key (`MappingReachable`, `internal/integrations/stripe/store/mapping_environment.go:89`), a rule written for a key the console cannot classify, which boot no longer accepts. So on such a deployment, an organization whose subscription the earlier key sold sees Cancel plan, Keep plan, Resume plan and the downgrade to a held or free rung on the Products page, because those moves buy nothing and read no price, and the Billing page draws Pay on an open invoice. Each plan move reaches a Stripe call made with no key, or an outbox entry that cannot run, and the member reads a failure; Pay returns the member to the Billing page without saying why. Background work asks the same question with no key: the sweep that applies scheduled plan changes (its schedule starts whatever the key), the invoice collection sweep and the reconcile's skip. The setup checklist's price step counts any recorded price mapping as done. ### What should happen With no Stripe key, no page offers a Stripe action and no background job attempts one, whatever mappings an earlier key left; the setup checklist does not count them. Whether the reach question answers no decides all of these, and what each page then shows needs deciding with it. ### Where `internal/integrations/stripe/store/mapping_environment.go`; `internal/server/plan_offer.go`, `billing.go`, `member_invoices.go`, `member_hosted_invoice.go`; `internal/fulfillment/sweep.go`, `collection_sweep.go`, `reconcile.go`, `plan_change.go` ### Why it matters A member on a deployment that removed its key is offered plan changes and payments that fail, and background jobs keep failing against Stripe with no key.

cgalo5758 added the

kind

bug

area/billing area/member-ui labels 2026-10-30 22:44:40 +00:00

cgalo5758 referenced this issue from a commit

2026-10-30 23:08:31 +00:00

Archive the one purchase rule and the site-bound requests changes

Sign in to join this conversation.