Suggested Test Cases

Test Cases

As you prepare for launching the Paze Service; we recommend the following test cases be reviewed andtested to ensure proper implementation, handling of error codes, and successful payment authorization. Not all test cases will apply to a Merchant and could be applicable to your Technical Integrator.

This document is used in conjunction with the Paze Merchant JavaScript SDK Technical Requirements document.


Test Cases

IDTaskSandboxProduction
1Successful Initialize requestXX
2Successful Can Checkout request & responseOptionalOptional
3Successful Checkout request & response(with expected data fields)XX
4Successful Complete request & response(with expected data fields)XX
5time is displayed properly in Paze pop upXX
6Ensure proper formatting of(ex. 9.90), two digits are required after the periodXX
7"Intent" aligns with the checkout flow:

- EXPRESS_CHECKOUT; consumer returned to final order confirmation page
- REVIEW_AND_PAY; consumer returned to order review page
XX
8Proper handling of consumer email address: if not passed in, Paze UI collects email:•       - If using CanCheckout, bypassCheckout requestXx
9Receipt of SMS OTP and successful authenticationXX
10Support of actionCode =
1.     CHANGE_CARD
2.     CHANGE_SHIPPING_ADDRESS
OptionalOptional
11Proper error handling for business and API error codes & Merchant error messages aligns to ConsumerNote: Ensure browser results and reason codes are handledXX
12Masked card data and consumer information isreceived and displayed properly on Merchantpage (checkout response) for purchase summaryand confirmation page/emailOptionalOptional
13type, ensure proper consent is collected from consumerOptionalOptional
14value is not reused across sessions (the same value should exist for therequests).XX
15Successful processing of authorization, settlement, refund on supported Networks:•       Visa•       Mastercard(If applicable: split shipments, multiple captures, subscriptions, etc.)n/aX
16Navigating back to Merchant page results in proper experience1.closes popup and returns to merchant page2. to merchant page3.                                                          closesUIand returns to merchant pageXX
17Test Paze flow across supported browsers:
Chrome
Microsoft Edge•       Safari
XX
18Checkout and Complete calls is set toXX
19s with consumerflows (shipping information is not prompted for in multiple locations during checkout).XX