Welcome to Zuora Product Documentation

Explore our rich library of product information

Default payment forms

Learn how to manage and customize default payment forms, including enabling features, configuring gateways, and handling user consent.

A default payment form is pre-configured on your tenant. You can directly use the default form, customize it, or easily set up a new one. You can manage customization easily, such as turning payment method types on and off by region, customizing additional form fields, switching between the vertical and horizontal layout, and updating themes promptly. Preview of changes is in real time.

Payment forms

Before you start

  • Enable Payment Form. Enable the Payment Form feature in Feature Management . You must have the Manage Payments Settings permission to access the Feature Management setting. For more information about this user permission, see Enable payment features by yourself .

    • In the Zuora UI, click your username in the upper right and navigate to Settings > Payments > Manage Features .

    • On the Payment tab, click Enable in the Payment Form row. A dialog describing that Zuora review is required for your enablement request is shown.

    • Click Enable Feature .

    • In the dialog, click Enable Feature , and then click Confirm To Enable .

  • Configure the default payment gateway. Ensure that a default payment gateway has been configured for the customer account or the tenant. By default, transactions triggered by payment forms are processed through the default payment gateway. The default gateway of the customer account takes precedence over the default gateway of the tenant. To override the default gateway, you can specify a gateway when implementing the backend API to create a payment session in your integration code.

    • For more information about how to specify the default payment gateway, see the following articles:

      • Billing and payment information for customer accounts

      • Set up payment gateways

    • For more information about how to override the default gateway, see "Implement backend API to create a payment session" in Payment Form Implementation Guide .

  • For Apple Pay and Google Pay, turn on the Payment Link feature and add your public business information.

    • Follow the instructions in Enable payment features by yourself to turn on the Payment Link feature.

    • Follow the instructions in Add public business information to invoice payment page to add the business name and web address of your company.

  • For PayPal, specify the payment gateway. Before adding the PayPal button to Payment Form, specify the payment gateway to process transactions triggered by the PayPal button in Payment Form:

    1. Click your username in the upper right and navigate to Settings > Payments > Setup Payment Page and Payment Link .

    2. Click the E-Wallets tab.

    3. In the PayPal section, click Select Payment Gateway .

    4. Select the payment gateway:

      • To use the Braintree v2.0 payment gateway integration, select Braintree from the list.

      • To use the PayPal Complete Payments payment gateway integration, select PayPal Complete Payments from the list, and then enter your Client ID obtained from PayPal. Contact PayPal to get this Client ID.

    5. Click Save .

Zuora’s Hosted Payment Form (HPF) provides configurable, regulation-aligned consent capture for cards, digital wallets, and bank transfers/direct debits. The feature ensures end users see the appropriate authorization text, can review merchant-provided consent or mandate language, and can accept or decline consent before a payment method is stored for future use. Admins can enable consent per payment method and by region, customize text and labels, and preview changes before publishing.

Bank transfer specifics (ACH, SEPA, PAD).

  • An authorization disclosure is always shown on the form (text is editable; it cannot be turned off).

  • A consent checkbox can be displayed; selecting it opens a modal dialog with creditor information, a consent statement, optional links (e.g., Privacy Policy/Terms), and Accept/Decline actions (labels customizable).

On acceptance, HPF records consent metadata (date/time, IP, payment method type, merchant/creditor info, consent source) and includes actions in the Stored Credential Profile.

What to do next

Understand and configure security measures for Payment Form. See Security measures for Payment Form .