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

ID

Task

Sandbox

Production

1

Successful Initialize request

X

X

2

Successful Can Checkout request & response

Optional

Optional

3

Successful Checkout request & response(with expected data fields)

X

X

4

Successful Complete request & response(with expected data fields)

X

X

5

time is displayed properly in Paze pop up

X

X

6

Ensure proper formatting of(ex. 9.90), two digits are required after the period

X

X

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

X

X

8

Proper handling of consumer email address:
• if not passed in, Paze UI collects email:
• If using CanCheckout, bypassCheckout request

X

x

9

Receipt of SMS OTP and successful authentication

X

X

10

Support of actionCode =
1.     CHANGE_CARD
2.     CHANGE_SHIPPING_ADDRESS

Optional

Optional

11

Proper error handling for business and API error codes and Merchant error messages aligns to Consumer

  • *Note**: Ensure browser results and reason codes are handled

X

X

12

Masked card data and consumer information is received and displayed properly on Merchant page (checkout response) for purchase summary and confirmation page/email

Optional

Optional

13

Type, ensure proper consent is collected from consumer

Optional

Optional

14

The value is not reused across sessions (the same value should
exist for their quests).

X

X

15

Successful processing of authorization, settlement, refund on
supported Networks:
•      Visa
•      Mastercard(If applicable: split shipments, multiple captures, subscriptions, etc.)
• Discover

n/a

X

16

Navigating 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

X

X

17

Test Paze flow across supported browsers:
• Chrome
• Microsoft Edge
• Safari

X

X

18

'transactionCurrencyCode used in Checkout and Complete calls is set to 'USD'.

X

X

19

'shippingPerference' which aligns with consumer flows (shipping information is not prompted for in multiple locations during checkout).

X

X