Manage User Consent on Payment Forms
Learn how to manage user consent on payment forms, including configuring consent capture for various payment methods and ensuring compliance with regulations.
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.
- An authorization disclosure is always shown on the form (text is editable; it cannot be turned off).
- A consent checkbox can be displayed on relevant payment methods (for example, cards, wallets, and non-BAV bank transfers); when present, selecting it will trigger the storage of that payment method for future use, while leaving it unselected will not.
- For ACH payment methods that use Bank Account Validation (BAV), the payment method is stored as part of the BAV flow and the checkbox to control storage is not displayed.
On each payment form, consent is configured for each of the following payment method group:
- Cards
Wallets (for example, Apple Pay, Google Pay, PayPal)
- Bank transfers / direct debits (for example, ACH, SEPA, PAD, BACS)
Zuora displays the controls you are responsible for the consent management to ensure that it complies with card network rules, wallet-specific policies, and each direct debit scheme’s requirements.
Zuora Payment Form also supports consent management for supported payment methods and now lets you localize consent-related text by locale. This means you can show consent checkboxes, authorization text, section labels, and dialog content in the same language as the rest of the payment form, which helps create a more consistent experience for your customers.
ACH with Bank Account Verification
When you use ACH with Bank Account Verification (BAV) through a supported provider, the consent configuration behaves slightly differently from other bank transfers:
- The authorization disclosure section is always available. You can edit this text, but you cannot turn it off.
- You can still enable and configure the User Consent Agreement so that a consent dialog is shown to end users before the payment method is stored as a means to confirm that the account information is correct and the user agrees to store this data.
- The explicit "Save Payment Method” checkbox and its associated text configuration are not shown for ACH with BAV, because the payment method is stored automatically as part of the bank account verification flow.
For ACH with BAV, make sure your authorization disclosure and any consent dialog text clearly explain that:
- The customer’s bank account will be verified, and
- The verified payment method will be stored and may be used for future payments according to your terms.
Localized consent experience
Localized consent text is supported for these payment method groups:
- Cards.
- Digital wallets, including Apple Pay and Google Pay.
- Bank transfer and direct debit payment methods, including ACH, SEPA, and PAD.
If you upload translated consent keys in your localization resource bundle, Zuora displays those translated values for the selected locale.
If a translated value is missing, Zuora falls back to the configured default consent text.