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 Case Tasks/IDs

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 request
Xx
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 and Merchant error messages aligns to Consumer
Note: Ensure browser results and reason codes are handled
XX
12Masked card data and consumer information is received and displayed properly on Merchant page (checkout response) for purchase summary and confirmation page/emailOptionalOptional
13Type, ensure proper consent is collected from consumerOptionalOptional
14The value is not reused across sessions (the same value should
exist for their quests).
XX
15Successful processing of authorization, settlement, refund on
supported Networks:
•      Visa
•      Mastercard(If applicable: split shipments, multiple captures, subscriptions, etc.)
• Discover
n/aX
16Navigating back to the Merchant page results in the proper experience

1. "Use another payment method" - closes popup and returns to merchant page.
2. User closes popup ('X') and returns to the merchant page.
3. "Continue to review" - closes the UI and returns to the merchant page
XX
17Test Paze flow across supported browsers:
• Chrome
• Microsoft Edge
• Safari
XX
18'transactionCurrencyCode used in Checkout and Complete calls is set to 'USD'.XX
19'shippingPerference' which aligns with consumer flows (shipping information is not prompted for in multiple locations during checkout).XX