Sandbox Testing
A guide to our Sandbox environment (https://api.sandbox.zeptopayments.com/payto) for simulating certain errors and behaviour.
Asynchronous Simulations
Within the API endpoints for our sandbox environment, we provide the ability to perform asynchronous simulations - such as simulating an agreement
being accepted, or a payment being settled automatically. This can be done using the sandbox simulate parameter (see below).
"sandbox": {
"simulate": "debtor_accept",
"delay": 0
}
Please refer to the documentation / schema for each endpoint for further information.
Testing Branch Codes
In our sandbox environment, we provide certain branch codes that will emulate the given institution having or lacking certain capabilities.
These can be used to receive certain validation errors (422) within the response to an API request.
For example, providing 100001
as the debtor branch code will result in a 422 response with an error code when creating an Agreement
.
These are described in the table below and can be provided for any party when creating an Agreement
, Amendment
or Payment
.
BSB | Simulated Behaviour |
---|---|
100-000 | Invalid BSB |
100-001 | Party institution does not have PayTo debtor capabilities |
100-002 | Party institution is not able to receive funds via SCT |
Updated about 3 hours ago