What checkout can refuse
Why a purchase can stop before it starts, what the delayed confirmation means, and why the answer is almost never to pay a second time.
Before you start and expected result
Have the checkout you started still open and note the exact message it showed. Do not begin a second purchase before reading this.
You know whether anything was charged, which check refused the purchase, and the safe next step other than paying again.
On this page
A workspace can have one checkout open at a time, and that checkout is written down before Stripe is ever called. Almost everything on this page follows from those two facts, including the reason a refusal is usually protecting you from a duplicate charge rather than standing between you and one.
Something else is already open
- Another checkout for this workspace is already open
You started a purchase somewhere else, on different terms, and it has not been finished or closed. Go back to it, or close it, then choose again. Two concurrent purchases on different terms is exactly what this prevents.
- This checkout is already being prepared in another tab
The same purchase, on the same terms, is mid preparation. It is not stuck. Wait a moment and try again, and it will hand you the session it was already building rather than opening a second one.
A previous payment is still being reconciled
An earlier subscription payment reached us and has not finished being applied. The workspace stays closed until it has been, and starting another checkout is refused rather than allowed to stack a second subscription on top of the unfinished one.
Contact hello@blogged.dev rather than retrying. This is the one refusal on this page that will not clear on its own.
Something changed while the purchase was being prepared
Between choosing a plan and paying for it, the thing being bought has to still be the thing you agreed to. Three checks run at that moment, and each stops before any money moves.
- This Project stopped being active
The Project was archived, or otherwise left the active state, while checkout was prepared. Nothing was charged. Refresh and start again.
- This Project's entitlement changed
The Project's signup benefit is no longer the one the purchase was priced against, usually because another session changed it. Nothing was charged. Refresh and review the current terms before continuing.
- Choose this Project's paid plan first
A Project created as a paid sibling has no plan yet, and setup, publishing and generation all refuse until it has one. This is not a failed purchase; it is the purchase not having happened yet. See creating a Project.
Confirming your subscription
After a successful payment you may see a short waiting state rather than the product: payment went through, and Stripe has not confirmed it to us yet. It usually clears in seconds.
If confirmation genuinely cannot be completed, the product says so in those words rather than leaving you on a spinner.
When delivery cannot be completed
Occasionally a payment succeeds and the exact entitlement it bought cannot be delivered: the set of Projects it was priced against changed underneath it, or reconciliation could not verify that Stripe holds exactly what our records say it should.
Blogged retries. After five failed attempts it stops, cancels the new subscription, and refunds the charge. Access stays closed throughout, which is the point: you are never left paying for a subscription that was never applied. In the rare case the reversal cannot be completed without a person, it is raised for support rather than left alone.
What none of this changes
No refusal on this page deletes content, cancels an existing subscription, or alters a Project's plan. Every one of them stops before the charge, or reverses it in full. Your posts, topics, knowledge and blog are untouched in all of them.