B. Sandbox environment

2. Code examples for sandbox

GitHub code examples for sandbox These code samples show you how to access the Sandbox with HMAC authentication (if you want to use HMAC in sandbox which is optional) and do the following things in sandbox:: get the status of the API create/get/delete a profile get...

read more

6. Payments inward – manual bank transfer

Bank transfer inwards sandbox simulation Customate Api has a separate endpoint that provides a way to create so-called “service payments”, for example, when clients want to emulate an external bank payment into a Customate wallet and make sure that integration works...

read more

5. Payment processing – direct debit

Direct debit errors Below is a table of test data and associated errors that can be used to simulate various problems during testing failed Direct Debit payments. Sort code Account number Error code Error message 400002 31001001 dd_no_instruction No instruction held...

read more

4. Funding source validation – direct debit

Validation errors - direct debit Below is a table of test data and associated errors, that can be used to simulate various problems during Direct Debit funding source validation. Sort code Account number Validation issue code Validation issue message 400002 31000001...

read more

3. Funding source and payee creation

Background to funding source and payees An external funding source (e.g. direct debit to pull money) and payees (e.g. external bank account to pay money to) can be assigned to a wallet. These first need to be created and the Customate platform validates these details...

read more

1. Introduction & Access

Background Customate provides a separate, isolated environment for clients. This environment, so-called sandbox, should serve as an excellent tool for developing and testing integration flow. Clients operate with virtual money during work in the sandbox, this...

read more