Skip to main content

Payment Pages


Payment Pages

This section of the tutorials provides an overview of Payment Pages 2.0. Use Payment Pages to quickly enable secure self-service payment capability for your subscribers.

About Payment Pages 2.0

Payment Pages 2.0 are customizable hosted payments pages that allow you as merchants to collect payments without the burden of PCI compliance. Payment Pages are hosted by Zuora and can be presented in an iFrame that you drop into your website. Payment Pages allow your subscribers to send payment details directly to Zuora in a secure, PCI-compliant manner. 

Unlike Checkout Pages that let your customers create a new account, subscribe to a product, and set up a payment method, Payment Pages only accept payments by letting your customers to set up a payment method. 

Payment Pages support the following types of payments: 

  • Credit Card
  • Automated Clearing House (ACH)
  • Single Euro Payments Area (SEPA)
  • UK Direct Debit

Key Concepts

Here are the key concepts to understand when implementing Payment Pages:

  • Payment Card Industry (PCI) CompliantTo accept credit card payment methods online, you (as the merchant) must achieve and maintain a level of security that meets the requirements of the Payment Card Industry. Payment Card Industry Data Security Standard (PCI DSS) is a set of requirements to ensure companies that process, store, or transmit credit card information maintain a secure environment. Zuora Payment Pages are fully PCI DSS compliant. The Payment Pages collect and transmit customer cardholder information safely and securely to Zuora's PCI compliant server
  • Dynamic Configuration: Use the Zuora JavaScript parameters to dynamically display your Payment Pages based on user locale and other criteria. For example, once you have added your translations, you can use the parameters to specify what label translations should be used and which gateway should be used to display and process the Payment Pages.
  • Client-Side Validation: When you enable the client-side credit card validation, the checks are performed as your subscriber enters a credit card number on the Payment Page.
  • Security Signature: To ensure security, requests to load your payment page must be digitally signed. Using the Zuora REST call, you generate the signature and pass that digital signature to your commerce page for it to access Payment Pages. 
  • Localization of Payment Pages: If your business serves global customers, you can create a dynamic and localized payment experience for each customer on Payment Pages. For each Payment Page, you can upload alternate translations for the labels, error messages, and texts on the form. You assign each of the uploaded translations to a locale to support multiple languages.

Additional Resources and Activities

To learn more about Payment Pages, see Payment Pages 2.0.

What's Next?

TryTeamCollaboration Tutorial: Configure a Payment Page