Payment received.
Access not created.
Fictional example — not a customer case study
Missing server-side fulfilment
Stripe marks the Checkout Session as paid. The webhook handler records the event ID, but creates no durable order or entitlement.
- Buyer impact
- The buyer can pay and still remain locked out.
- Related symptom
- The success page trusts the redirect instead of server-verified order state.
Repair the fulfilment boundary first
- Create an authoritative server-side order record.
- Verify the webhook signature and make fulfilment idempotent.
- Render the success state from the verified order.
- Verify the agreed payment-to-access path.
Illustrative repair order from the public sample. A real scope depends on the project’s evidence and approval.
What must be true after the repair
- A completed session creates exactly one order.
- Repeated events do not duplicate access.
- Paid access follows server-confirmed fulfilment.
- Failed or unpaid sessions never grant access.
Illustrative checks, not executed tests or a delivered customer result.