Merchants may integrate with Paze directly or indirectly depending on their existing tech stack and how they work with their service providers. Paze supports Merchants that have in-house commerce and payment processing capabilities, as well as Merchants that work with service providers for one or both of those functions.

In general, a Merchant’s Paze integration should follow the pattern below, with additional degrees of complexity added at the Merchant’s discretion. Error states have been omitted for clarity.

Integration Process

Action	Response
Consumer enters the cart or account management page	Commerce site invokes initialize API to start running fraud checks
Consumer initiates Paze	Commerce site invokes checkout API to launch the Paze user interface (UI)
Consumer selects payment and shipping information and exits the Paze UI	Commerce site displays the consumer details sent by Paze
Consumer chooses to change selected payment card or shipping information	Commerce site invokes the checkout API to relaunch the Paze UI
Consumer selects payment or shipping information and exits Paze UI	Commerce site displays the updated consumer details sent by Paze
Consumer finalizes purchase	Commerce site invokes the complete API to initiate the transaction
Paze generates encrypted payload for transaction	Commerce site provides payment processor with encrypted payload’s identifier Paze sends encrypted payload to merchant
Merchant decrypts encrypted payload and submits it for processing	Commerce site displays transaction success message to consumer

Service Provider Implementation

can be requested directly through the Merchant JavaScript SDK or Merchant Mobile API Technical Requirements. This precludes the use of the Merchant Business-to-Business API.
For Merchants using a platform that provides both commerce and payment processing, that platform must integrate with Paze directly. That platform can integrate with Paze as if it is a Merchant with consolidated commerce and payment functions.
For Merchants that have separate providers for commerce and payment processing functions, the payment processor can receive the encrypted payload in two ways:

The commerce site requests the full encrypted payload from Paze. Upon receipt, the commerce site transmits the payload to their payment processor.
The commerce site requests the payload identifier from Paze. Upon receipt, the commerce site transmits the payload identifier directly to the payment processor. The payment processor uses the payload identifier to request the full encrypted payload from Paze.