A. API testing in Sandbox Mock

Reminder: we only process fake data in Sandbox Mock environment.

For more informations, read this guide:

Sandbox guide - VOP

Test the Qombo API in the following order:

1. Request

   Use the Verify endpoint to make a verification on our fake data.

   <aside> 📄

   Please find the documentation of the /verify endpoint here.

   </aside>

   All requests are sent to the fake banks:

   • Bank One - BANKONEXXXX - IBANs starting with FR11
   • Bank Two - BANKTWOXXXX - IBANs starting with FR22

   The list of user accounts of these banks are visible on this page:

   Sandbox / IBAN dataset

<aside> ⚙

To test, two options:

• use the manual verification form of the Qombo Platform
• use the Postman collection to call the Qombo Verify endpoint

Compare the results you get with the data of fake banks.

</aside>

1. Expose

   Use the Expose endpoint to send fake account holders data.

   <aside> 📄

   Please find the documentation of the /expose endpoint here.

   </aside>

   Please send fake or anonymous data. This will be saved in our sandbox database.

   <aside> ⚙

   To test:

   • use the Postman collection to call the Qombo Expose endpoint

   Check on the Qombo Platform > Accounts that the data is properly saved.

   </aside>

2. Respond

   Call the Qombo API as an external bank to test a verification on the fake data you imported.

   <aside> ⚙

   To test:

   • use the Postman collection to call the Qombo Payee Verification endpoint

   Compare the results you get with the fake data you imported with Expose.

   </aside>

Once these three API calls have been validated, you can integrate them in your workflows and start the 2nd step.

B. End-to-end API testing in Staging / Pre-production

Prerequisites:

To begin this second step and process external VoP requests, you must:

• Process sufficient tests in Sandbox Mock environment (Requesting & Responding)