Integration Basics




The use of Paze®Service requires the participation of a Distributor (e.g. FiServ, WorldPay) who will contract with the Merchant and approve the distribution of production keys. The following outlines the steps to register and move to production, including available support channels.

Note: A Merchant’s Distributor or Technical Integrator may be responsible for some or all of the of the outlined steps below. Coordinate with your Distributor and or Technical Integrator on your required responsibilities.

Onboarding

Register

  • Work with your Distributor (or Technical Integrator (e.g. CyberSource), as applicable) on their specific onboarding process, it may include Merchant to complete the Paze Merchant Setup Form, as part of registration a Rivest–Shamir–Adleman (RSA) certificate is required by the party managing the decryption of Paze payload.
  • A sandbox account is created for Merchant.
  • Sandbox credentials delivery methods vary depending upon technical implementation.
    • Option 1: Paze Merchant Support Team sends credential to Merchant through secure email
    • Option 2: Distributor sends credential to Merchant
    • Option 3: Technical Integrator sends credential to Merchant
  • As required, test Paze wallets are created for testing the Paze checkout experience in a lower environment.
  • Logo assets will be shared by Paze Merchant Support Team

Integration and Go Live

Integrate

  • Merchant (Technical Integrator or Distributor depending upon technical implementation approach) completes technical integration to applicable specifications following best practices, including integrating Paze into their digital property
  • Present Paze per the Paze Checkout User Interface Standards Guide

Test

  • Merchant tests in sandbox.
  • Pre-defined test cases are available for sandbox testing.

Launch

Dependency: Merchant signs Agreement with Distributor related to Paze Service

  • Production access and release of credentials are managed by Merchant’s Distributors; credential generation and delivery methods vary depending upon technical implementation
    • Option 1: Sent to Merchant through secure email
    • Option 2: Distributor sends credential to Merchant
    • Option 3: Technical Integrator sends credential to Merchant
  • Merchant to provide contact details to Paze for notifications regarding documentation changes, production releases, outages, etc.

Paze Mobile Components

Paze mobile components are available for Android (Jetpack Compose, XML Views) and iOS (SwiftUI, UIKit). The mobile components provide pre-built button and message UI that matches the web SDK experience.

Talk to your account manager to get the mobile component source files.