Introduction

The Paze^SM Merchant JavaScript SDKprovides information about Application Programming Interfaces (APIs) used to return tokenized payment information as well as appropriate checkout details. This document describes the JavaScript (JS) Software Development Kit (SDK) for APIs to be used in a Merchant’s front-end implementation.

There are four available APIs discussed in this guide:

1. Initialize: Passes in the assigned Merchant identifier (issued during onboarding) and initiates fraud systems for a secure checkout.
2. Checkout: Runs the complete digital wallet consumer-facing flow (including lookup, authentication of consumer, and consumer information selection) and returns a summary of the card and address selection.
3. Complete: Closes the Merchant and consumer sessions and provides payment details required to successfully process the Payment Transaction, whether the consumer intends to make a payment immediately, indicates a card to be put on file with the Merchant, or both.

Sensitive payment data can also be accessed via the direct Merchant B2B API documented in a separate guide.

Note: Complete must still be called to close the session even if the B2B API is being used.

The JavaScript APIs will use Promise objects that represent the eventual completion (or failure) of an asynchronous operation and its resulting value.

Prerequisites

To use these APIs, Merchants must establish a relationship with an approved Paze Distributor that will sponsor and onboard the Merchant. Upon onboarding, Merchants will be assigned entity identifiers (such as API keys and profile IDs) and exchange required cryptographic material.

Detail Table – Column Definitions

The following sections contain tables of fields with one or more of the columns described below.

• Required – Must be provided
• Optional – Can be provided when available and/or applicable
• Conditional – Must be provided if certain other fields are populated