Collaction Transaction Test

In the testing environment, PayerMax provides comprehensive simulation strategies to facilitate merchants in debugging the processing flow of different payment results during the integration process.

1. Result Simulation

1.1 Redirect-based payment methods:

During merchant integration testing, merchants can select the payment method and enter payment information in the correct format to initiate a simulated payment on the simulation interface. (In the testing environment, no actual deduction takes place; the simulation only verifies the format of the payment information and does not validate the authenticity of the account.)

The acceptance method and expected results are as follows:

• Payment successful: The foreground page will enter to the success result page, and the server will immediately get a callback notification of the success status.
• Payment failed: The foreground page will enter to the failure result page. If you need to inspect and accept the failure status callback of the server, please click the Close button in the result page to close the cashier page.
• Pending: The foreground page will enter to the pending page. The server will not receive a callback.
  

1.2 Direct payment methods (card payments, OTP payments, authorization payments excluding Taiwan, pure API):

• If success, any amount except the fixed amounts listed below;
• If failed, fixed amount (local currency) can be set: 15, 500, 1.12, 20000, or 25000;
• If pending, fixed amount (Local currency) can be set: 6、 60、600、16000.
  

Please note that the totalAmount you set must be within the limit of the current payment method.
Simulate 3ds certification:Passing in a specific amount of 222 can simulate 3ds authentication. If 3ds chooses authentication to be successful, the payment will be successful. If 3ds chooses authentication to fail, the payment will fail.

For card payment, in UAT environment testing, please use the following test card numbers:

Visa	Master
Card No.: 4444333322221111 Name: James Smith Expiration Date - Y: 25 Expiration Date - M: 03 CVV: 123	Card No.: 5555555555554444 Name: Allen Black Expiration Date - Y: 26 Expiration Date - M: 11 CVV: 357

Saudi Mada	Kuwait Knet	Qatar Naps	Bahrain Benefit	Pakistan
Card No.: 5297412542005689 Name: William Harris Expiration Date - Y: 25 Expiration Date - M: 05 CVV: 350	Card No.: 4507785555554449 Name: Jacob Thomas Expiration Date - Y: 26 Expiration Date - M: 11 CVV: 357	Card No.: 4215375500883243 Name: Olivia Taylor Expiration Date - Y: 26 Expiration Date - M: 06 CVV: 123	Card No.: 5326774027281753 Name: Brown Jenny Expiration Date - Y: 30 Expiration Date - M: 08 CVV: 927	Card No.: 4919713330643198 Name: Patric berg Expiration Date - Y: 2027 Expiration Date - M: 06 CVV/CVC: 135

Payment method	Card number	Name	Expiration date - M	Expiration Date - Y	CVV
Visa	4444333322221111	James Smith	03	25	123
Master	5555555555554444	Allen Black	11	26	357

Google Pay Mock:

(1) Select “Google Pay” on the cashier page, and pull up the Google Pay payment sheet.

(2) Login to Your Google Account, you can add your Gmail to the Google test card suite group(https://groups.google.com/g/googlepay-test-mode-stub-data ) for the next simulation payment.

(3) After the Google Pay authorization is completed, it will return to the PayerMax simulation result page to simulate the payment success or failure. For details, see【Google Pay UAT Simulation Process】

Note:

Pulling up GooglePay sheet in WebView is not supported.

2. Test Cases

After completing the product capability access, in order to help merchants verify the correctness of Collection product functions and understand expected behaviors of each API, PayMax provides developers with complete test cases. You can download on demand according to different integration modes in actual docking:

(1) 【Cashier Payment】
(2) 【Direct API】
(3) 【Payment Tokenization】
(4) 【Front-end Component】
(5) 【PayByLink】
(6) 【ISV Cashier Payment】
(7) 【ISV Direct API】