Members reach a payment page headed by a name the console never showed them #13

New Issue

2026-09-21T07:18:05Z

cgalo5758 commented

2026-09-21 07:18:05 +00:00

What a person cannot do today

Learn who will charge their card before they are on the payment provider's page. Subscribing hands off to Stripe Checkout with a bare redirect, and that page is headed by the Stripe account's public business name, which Stripe fills from the account's registered legal name until the operator sets one. Where that legal name differs from the deployment's own, the first time a member reads it is above the card fields, on a page that is not the console's.

What they should be able to do

Read the merchant of record on the console's own billing page before the hand-off, and, as the operator, see on the console the name Checkout is going to display.

Why it matters

Two independent walks of the purchase path reported the same surprise: the page that asks for a card is headed by a name nothing in the product introduced. That reads as a misdirected payment and is reason enough to abandon the purchase. It is also the operator's only warning that an account setting they have never opened is member-facing.

Where

internal/server/billing.go, the checkout hand-off; the member billing page; the Stripe integration page template and the setup readiness check.

Done when

The Stripe integration page and the readiness check read the account back (the business profile name, the branding settings and the statement descriptor) and show the name members will see, flagging an unset one the way the environment check flags a stale price; the member billing page states the merchant of record from the same read before the hand-off; and the deployment documentation lists setting the public business name, icon and statement descriptor, on the live account and the test account both, as a setup step.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today Learn who will charge their card before they are on the payment provider's page. Subscribing hands off to Stripe Checkout with a bare redirect, and that page is headed by the Stripe account's public business name, which Stripe fills from the account's registered legal name until the operator sets one. Where that legal name differs from the deployment's own, the first time a member reads it is above the card fields, on a page that is not the console's. ## What they should be able to do Read the merchant of record on the console's own billing page before the hand-off, and, as the operator, see on the console the name Checkout is going to display. ## Why it matters Two independent walks of the purchase path reported the same surprise: the page that asks for a card is headed by a name nothing in the product introduced. That reads as a misdirected payment and is reason enough to abandon the purchase. It is also the operator's only warning that an account setting they have never opened is member-facing. ## Where [`internal/server/billing.go`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/server/billing.go), the checkout hand-off; the member billing page; the Stripe integration page template and the setup readiness check. ## Done when The Stripe integration page and the readiness check read the account back (the business profile name, the branding settings and the statement descriptor) and show the name members will see, flagging an unset one the way the environment check flags a stale price; the member billing page states the merchant of record from the same read before the hand-off; and the deployment documentation lists setting the public business name, icon and statement descriptor, on the live account and the test account both, as a setup step. Migrated from status/issues.md at b7a0e15

cgalo5758 added this to the Public launch milestone 2026-09-21 07:18:05 +00:00

cgalo5758 added the

kind

enhancement

area/billing area/operator-ui area/member-ui

priority

high

labels 2026-09-21 07:18:05 +00:00

Sign in to join this conversation.