This documentation page outlines the testing process for payment and payout integrations.
The purpose of this testing is to ensure that the integration runs smoothly and without any issues.
Through a series of test scenarios, including changes in payment and payout statuses, we verify that the integration is functioning correctly and that all transactions are properly processed.
This testing is an essential step in ensuring the reliability and effectiveness of the integration.
We will be testing a total of 6 transactions, which includes 3 payments and 3 payouts.
Our goal is to cover all possible scenarios that could occur in a production environment.
Once we receive the Unique Identifiers (UIDs) for these transactions, we will proceed with changing their status to simulate various scenarios.
During this testing process, we will walk through each scenario step-by-step, explaining them in detail as needed, before moving on to the next one.
If any of the test flow test cases fail, we will halt the testing process until the issue is resolved.
This is to ensure that any further tests will not be impacted by the issue, and that we can maintain the reliability and consistency of the integration. Our goal is to deliver a high-quality integration.
|Payment Flow Validation|
We perform 3 tests to cover different payment scenarios
|Test 1: Change status from pending to paid|
|Test 2: Change status from pending to expired|
|Test 3: Change status from pending to denied|
|Payout Flow Validation|
We perform 4 tests to cover different payout scenarios.
|Test 1: Change status from pending to onhold (2 transactions)|
We require two transactions with the "onhold" status for payouts: one for use in Test 2 and the other for Test 3.
|Test 2: Change status from onhold to success|
|Test 3: Change status from onhold to failed|
|Test 3: Change status of a success transaction to refunded|
This scenario happens when the customer or the bank entity refunds the amount to our bank account for some reason.
In this case, the amount must be returned to the customer.
When this happens, our suggestion is to refund the customer through your platform so that they can make a new payout request.