X5 Sandbox and simulators
Break it on purpose, before it breaks on its own.
A sandbox where everything succeeds tells you nothing you need to know. This one runs the same code as production with deterministic rail simulators, and you can inject the failure you are worried about rather than waiting for it.
Scenarios you can inject.
Each is a request away, and each behaves the same way every time, so a test that passes today passes tomorrow for the same reason.
The states a payment can reach.
Every one of these is reachable in the sandbox on demand, including the terminal ones you would rather not meet in production first.
Where else it can go
Every non-terminal state carries a deadline and a named consequence. A rail that stops answering becomes SUBMITTED_UNKNOWN, which is queried rather than resent, because the one thing worse than an unknown payment is two of them.
What it guarantees.
Each of these is enforced rather than intended, and each is something you can sit down and try to break on a call. We would rather you did.
- The sandbox runs the same build as production. It is seeded differently, not written differently, so a behaviour you see here is a behaviour you will get.
- Simulators are deterministic. The same scenario produces the same sequence every time, which is what makes a test suite worth running.
- Test data is generated to a seed, so two engineers can describe the same customer to each other by name.
- Nothing in the sandbox can reach a real rail, a real provider or a real customer.
Ask for sandbox credentials.
You do not need a signed contract to start building against it, and we would rather you found the awkward parts early.