For developers
Build against it before you commit.
Issue a key, switch on test mode, fire a synthetic payment, and read exactly what your integration sent.
Keys
Issue one. Revoke it the moment you want to.
A key belongs to your account and reaches nothing outside it.
Revoking one takes effect
straight away.
Issue
Create a key from the developer screen and copy it once.
Use
Every call carries the key, and every call is scoped to your account by it.
Revoke
Retire a key at any time, and the revocation is recorded with the rest.
Webhooks
Told what happened, with proof it was us.
Subscribe to the events you care about.
Each delivery carries a signature your side
checks before acting.
Setting it up
Keeping it healthy
Test mode
A whole sandbox, switched on with one control.
Fire synthetic payments, script a scenario, reset the lot and start again.
Nothing you
do in test mode touches anything real.
The sandbox
Scenarios
Seeing what happened
A write that arrives twice happens once, so a retry stays safe.
Point a test integration at OrchesPay.
Thirty minutes. We issue a key, switch on test mode and fire a payment together.
hello@orchespay.com