Service Provider Implementation

There are multiple service provider implementation options:

• In-House Processing
  Merchants handling both commerce and payment processing in-house can request the encrypted payload directly through the Merchant JavaScript SDK (no Merchant B2B API required).

• Consolidated Platform
  If a Merchant uses a platform that provides both commerce and payment processing, the platform must integrate with Paze^SM
  directly — as if it were a Merchant with consolidated 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 and transmits it to the payment processor.
  • The commerce site requests only the payload identifier from Paze and sends that identifier directly to the payment processor, which then requests the full encrypted payload.