Test store
Developers
A demonstration shop that opens a real checkout page in test mode.
No money moves — it is the simulation rail answering — but webhooks, developer logs and receipts all fire exactly as they do in production. It is the fastest way to see the whole loop.
Choosing the outcome by the amount
The last two digits of the amount decide the outcome:
| Ends in | What happens |
|---|---|
99 |
Permanent decline |
98 |
Temporary decline (rail unavailable) |
97 |
Accepted, then fails |
| anything else | Success |
The
97case deserves the most attention. A payment accepted and then failed is the sequence webhook handlers most often forget — and it is the one that costs the most in production.
The four products in the window cover those four cases; the custom amount field composes any other.
That field is in minor units, and it takes digits. Group separators are fine — type 1,500 or
1 500 and it reads 1500 — but a decimal point is refused rather than guessed: in minor units
15.00 could mean 1500 or 15, and the field will not choose for you.
— /dashboard/test-store