Paze℠ Processing

Paze makes it easy for shoppers to make purchases. Offered by participating banks and credit unions, Paze enables shoppers to check out online without having to share their actual card numbers with merchants.

You can read more about the benefits here: https://www.paze.com/

Paze is a product offered by Early Warning Services, LLC, the same company behind Zelle®, the popular person-to-person payment option.

Merchants can integrate with Paze directly based on their existing technology stack and relationship with Radial. The integration process typically involves several steps, including invoking APIs to initialize fraud checks, launch the Paze shopper interface, update consumer details, and finalize purchases. The process also involves generating encrypted payloads for transactions and handling communication between the commerce site, payment processor Radial, and Paze.

The benefits of integrating Paze include:

  • Streamlined Checkout: Paze simplifies the checkout process by storing payment, contact, and shipping information in a digital wallet. This allows shoppers to complete transactions quickly without repeatedly entering their details.
  • Faster Transactions: The Paze interface enables faster payment processing, reducing the time shoppers spend at checkout.
  • Tokenization: Paze uses tokenized payment credentials instead of storing actual card numbers. This reduces the risk of fraud and data breaches, as compromised tokens can be deactivated without affecting the shopper's actual card.
  • Encryption and Signature: Transactions are secured with strong encryption (RSA-OAEP-256, A256GCM) and digital signatures (RS256), ensuring data integrity and confidentiality.
  • Multiple Initiation Points: Paze offers static, dynamic, and automatic initiation options, allowing merchants to tailor the payment experience based on consumer preferences and behaviors.
  • Checkout: Paze can be used for both guest and registered shopper transactions, offering a seamless experience regardless of the consumer's status.
  • Account Creation: Paze streamlines account registration by pre-filling consumer information and setting up cards on file during the account creation process.
  • Card Updates: Registered shoppers can easily update their payment credentials through the Paze interface, ensuring their information is always current.
  • Onboarding and Integration Support: Merchants receive detailed guidance and support throughout the onboarding, integration, testing, and production phases.
  • Simulation and Test Environments: Merchants can use simulation and test environments to validate their integration and ensure everything works correctly before going live.

Onboarding Steps

Radial

  • Radial takes care of the merchant's application for offering Paze, including gathering credentials to support various use cases, channels (mobile web, app, desktop), or subsidiaries (for example., multiple brands under the same holding company).
  • Radial provides merchants with “profileId” parameters to use in their requests.

Merchants

  • The Merchant completes JavaScript SDK technical integration according to applicable specifications and best practices, including integrating the Paze button into their sites.
  • Merchants perform testing in the Paze sandbox environment.
  • Pre-defined test data is available for sandbox testing.

Paze Process Flow

The following detail provides a step-by-step overview outlining the interactions between the Shopper, webstore, Paze, Radial, and the card network issuer during the Paze payment process.

  1. The shopper navigates to Checkout Page:

    • Action: The shopper goes to the checkout page on the webstore.
    • Webstore: The webstore initiates loading the checkout components.
    • SDK Load: The Paze JavaScript SDK is loaded as part of the checkout page setup.

  2. Initialize API:

    • Action: The webstore invokes the initialize API to start the Paze process.
    • API Request: A request is sent from the webstore to Paze to initialize the shopper session.
    • Response Handling: Paze returns a JavaScript resolve or reject response to the webstore based on the initialization success.

  3. Load Paze Payment Option:

    • Action: The webstore prepares and presents the payment options available to the shopper.
    • Paze Option: The option to use Paze for payment is included among the available payment methods.

  4. The shopper enters their email Address:

    • Action: The shopper enters their email address into the designated field on the webstore’s checkout page.
    • Webstore: The email address is captured and prepared for verification with Paze.

  5. CanCheckout API:

    • Action: The webstore invokes the canCheckout API to verify if the consumer is eligible to proceed with Paze.
    • Eligibility Check: Paze checks the shopper's registration and eligibility status.
    • API Response: Paze confirms whether the shopper is registered and eligible to proceed.

  6. Display Paze button:

    • Action: The webstore evaluates the response from Paze.
    • Button Display: If the response indicates that the shopper is registered with Paze, the webstore displays the Paze button as an available option for proceeding with the payment.

  7. The shopper clicks the Paze Button:

    • Action: The shopper clicks the Paze button to select it as their payment method.
    • Button Interaction: This shopper action triggers further Paze-specific processes.

  8. Launch Paze UX:

    • Action: The webstore invokes the checkout API to launch the Paze shopper interface (UX).
    • UX Launch: The Paze checkout UI is displayed to the shopper for further interaction.
    • Shopper Action: The shopper completes authentication within the Paze UI and selects their payment card.

  9. JavaScript Checkout API Response:

    • Action: Paze sends a JavaScript response back to the webstore indicating the result of the checkout process.
    • Review Page: The webstore displays a transaction review page to the shopper based on the response data.
    • Shopper Review: The shopper reviews the transaction details presented on this page.

  10. The shopper confirms the transaction:

    • Action: The shopper confirms the transaction by clicking the confirmation button on the review page.
    • Webstore: This action triggers the next step in the transaction process.

  11. Complete API:

    • Action: The webstore invokes the complete API to finalize the transaction.
    • API Call: A request is sent from the webstore to Paze to complete the transaction process.
    • Response Handling: Paze returns a JavaScript response with the complete payload to the webstore.

  12. Submit encoded complete API response:

    • Action: The webstore submits the encoded complete API response to the Radial PSP for processing. Refer to Credit Card Wallet Authorization Request.
    • Data Transfer: The encoded payload is securely transferred to the PSP.

  13. Radial PSP processing:

    • Decoding and Verification: The Radial PSP decodes, verifies, and decrypts the payload received from the webstore.
    • Transaction Submission: The PSP then submits the transaction details to the card network issuer for approval.

  14. Card network issuer approval:

    • Approval Process: The card network issuer processes the transaction request.
    • Approval Notification: Upon successful processing, the card network issuer approves the transaction and notifies the PSP.

  15. Display confirmation page:

    • Action: The Radial PSP confirms the transaction approval to the webstore. For the response from Radial, refer to Credit Card Wallet Authorization Response.
    • Confirmation Display: The webstore displays a confirmation page to the shopper, indicating that the transaction has been successfully completed.