There are multiple service provider implementation options:

In-House Processing
For Merchants that handle both commerce and payment processing in-house, the encrypted payload 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.
Consolidated Platform
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.
Separate Providers
For Merchants with separate providers for commerce and payment processing, the payment processor can receive the encrypted payload in one of 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.