The Payment Provider Is Down on Launch Day
Work from the brief alone. Write what you would produce — actors, requirements, data, a first slice, your unknowns — before opening anything below it; the exercise stops working if you read the reality first.
The store bought its payments. On launch day the provider has an outage lasting hours (illustrative). Design, in advance, what the customer sees, what the store records, what happens to stock, and what the recovery is when the provider returns — without building a second provider integration unless you can justify its operating cost.
Your attempt
Nothing here is checked. It exists so that the reveal below is a comparison rather than a reading.
Integrating a second provider "for resilience" before launch. It doubles the integration surface, adds a routing decision that can itself fail, creates two ledgers to reconcile, and is paid for every month — to cover an outage whose cost nobody has measured, on a store that has not yet processed its first real order.
Read this even if you are confident. It is here rather than behind a button because it is the move most people actually make, it produces things that look like a project, and its cost arrives when the first hard requirement has nowhere to go.