Home

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.

01

Issue

Create a key from the developer screen and copy it once.

02

Use

Every call carries the key, and every call is scoped to your account by it.

03

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

Configure the address that receives them Live
Subscribe to the events you want Live
Rotate the signing secret whenever you like Live
Fire a test delivery on demand Live

Keeping it healthy

A log of every delivery attempted Live
Retry one that failed Live
See the response your side returned Live
A catalogue of every event you can subscribe to Live

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

Switch test mode on and off Live
Create synthetic payments Live
Reset the sandbox to empty Live
Fire a test call at your own endpoint Live

Scenarios

Script a sequence of events Live
Run it and watch the result Live
Keep a history of every run Live
Rerun one after a change Live

Seeing what happened

A log of every request your integration made Live
The response each one received Live
A status page you can subscribe to Live
Access controls, roles and sessions Live

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