The Payment Form feature is designed to modernize the payment integration experience, providing a seamless, scalable, user-friendly, and PCI-compliant hosted payment form solution for collecting payments. It offers the following key advantages:

• Minimal code experience in managing payment methods and payment information on the hosted form

• Dynamic presence of payment method options and information to the buyer for a higher conversion rate

• Elimination of the need for managing multiple iframes thus reducing complexity

Custom submit for Payment Form

Payment Form supports the ability to define a external submit button for businesses that need more control over the customer journey.

With external submit, you can:

• Display Zuora-hosted payment fields on your site without submitting them immediately.

• Let customers complete other steps, such as sign-up or consent, before submission.

• Place your own submit button anywhere in your experience and trigger submission when the customer is ready.

This capability is available for Credit Card, ACH, SEPA, PAD, and PIX payment forms, and is designed to extend to future Payment Form types.

Payment methods created through external submit use the same underlying payment method model as the standard Payment Form flow.

All payment methods available for a region are consolidated into a single payment form. In the Zuora UI, you can easily enable or disable payment methods by region. The following image shows examples of payment forms in vertical and horizontal layouts.

Support for payment gateway routing

Payment Gateway Routing is a feature powered by Zuora, which allows you to route transactions to preferred payment gateways and to handle fallback scenarios in case those transactions fail. For more information, see Overview of Payment Gateway Routing.

Zuora does not support the Payment Gateway Routing feature for Zuora's hosted payment method page (HPM) solution, Payment Pages 2.0.

Supported Browsers

Desktop browsers are supported as described in Supported browsers.

Pre-populated customer data

Hosted Payment Form supports pre-populating non-sensitive customer data when you create a payment session. You can pre-fill fields such as email address, phone number, and billing address so customers can complete checkout faster with less manual entry.

This capability is especially useful if you already collect customer contact or billing details in your checkout flow or if you are migrating from Hosted Payment Method to Hosted Payment Form and want a similar pre-fill experience.

You can also control whether each pre-populated field is visible on the payment form. Hidden fields are still submitted with the payment.

This feature is optional and does not affect existing integrations that do not use it.

Pre-populated customer data is supported only payment methods which support the collection of these fields within the Payment Form.

If you use Apple Pay with Payment Form, you can now configure billing address, email address, and phone number fields for Apple Pay in the Payment Form editor.

This allows Apple Pay checkouts to capture and store customer billing details if they already exist within the wallet, helping streamline checkout and reduce manual and redundant follow-up for missing information.

Customer action required: Update your Payment Form configuration only if you want these Apple Pay fields to be shown or collected in the hosted form experience. Otherwise, no configuration change is required.

Payment Form supports a multi-step flow in which payment details can be collected first and submitted later.

A typical flow works as follows:

• The customer enters payment details in Zuora-hosted fields.

• The customer completes other steps in your experience, such as onboarding or consent.

• Your application triggers submission from your own button.

• Payment Form submits the data and creates or validates the payment method.

Compliance

The payment forms implemented through the Payment Form feature are PCI-compliant.

Limitations

• 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 through the Create a payment session API operation in your integration code.

• Zuora does not assign a fallback gateway for transactions that go through the 3DS2 flow.

• Zuora does not support Gateway Routing for the Apple Pay payment method in the Payment Form.

Resources

• Configure payment forms

• Payment Form Implementation Guide

• Payment Form integration sample code

• Security measures for Payment Form

• For any questions, contact Zuora Global Support .