Web Client SDK Setup

The following JavaScript endpoints are available for use during testing and production.

JavaScript SDK Endpoints

Environment	JavaScript SDK Endpoint
Sandbox	Provided at time of onboarding
Production	Provided at time of onboarding

Before calling Initialize, Merchants must load the Paze^SM SDK. The SDK creates a popup that is used to host the user interface (UI) for the SDK.

The following example shows how to load the SDK and create an adapter:

<head>
</head>
<body>
  <script src="https://ProvidedatTimeOfOnboarding"></script>
  <script>
    let digitalWalletAdaptor = window.DIGITAL_WALLET_SDK;
  </script>
</body>

When presenting any SDK UI, the SDK controls the seamless operation of the window as a popup.

Providing Keys and Certificates

As a Paze Participant, a Merchant must use a key for source validation and for decrypting payloads. These keys are provisioned during Merchant onboarding. Asymmetric data encryption keys are supported and require a public certificate from the entity performing the decryption.

Keys

Key Description	Purpose	Key Type
Payload Verification	Merchant verifies the signature by obtaining the certificate hosted by Paze on a well-known URL. Paze signs the payload.	Asymmetric
Payload Decryption	Merchant decrypts the full payload.	Asymmetric

Authentication Endpoints

Paze will host its authentication certificates at the following URLs.

Authentication Endpoints

Environment	URL
Testing	Provided at time of onboarding
Production	Provided at time of onboarding