On This Page

Two Paze Decryption Methods

Integration hooks for two Paze decryption methods are built into the

Cybersource

payment management platform. The two decryption methods—merchant decryption and

Cybersource

decryption—handle Paze encrypted payment data differently. You will integrate the decryption method that best suits your technical development environment in terms of desired degree of exposure to, or control over, sensitive payment information.

IMPORTANT

The Paze decryption method that you integrate determines how you will format your API request messages when you authorize a payment.

Merchant decryption: For merchant decryption, you (the merchant or the integrator) are responsible for the generation of the payment encryption keys, decryption of the payment response payload from Paze, and mapping the information—including the Paze payment token—to the corresponding Cybersource REST API fields for an authorization request. With merchant decryption, payment instrument details remain visible to you, and you control the technical development that decrypts this information.
Cybersource decryption: For
Cybersource
decryption, you integrate the Paze wallet directly on your checkout page.
Cybersource
creates and manages the Paze decryption keys and extracts and decrypts the sensitive payment information on your behalf. Having
Cybersource
process your Paze transactions reduces your PCI compliance burden. For information about the PCI Data Security Standard (DSS), see the PCI Security Standards Council.

IMPORTANT

The Paze decryption method that you integrate determines how you will format your API request messages when you authorize a payment.