Define test cases
- Identify core scenarios . Develop a set of test cases that cover different payment operation types, payment methods, and currencies.
-
Obtain test card and account information
.
Obtain the test card and account information from the gateway provider. Payment gateways often offer specific card numbers to trigger particular outcomes, such as approvals or declines. Here are some examples:
-
Stripe test cards
-
Checkout.com test cards
-
EBANX test cards
-
-
Prepare error code testing
.
Confirm with your gateway provider which error codes the gateway supports and their use cases. Simulate them to verify the error-handling functionality. Different payment gateways offer different magic values to simulate gateway-side error codes in their test environments. You need to follow the gateway provider’s test instructions to simulate corresponding error codes.
For example, Chase Orbital uses payment amount value to simulate an error code. When your payment amount is
571, the test environment of Chase Orbital returns the following codes and message:-
Payment error code:
09 -
Payment error message:
Revocation of Authorization -
If you review transaction details in the response string in Zuora's payment transaction log, you may find the Orbital Host response code
571.
-