Zuora Payments glossary
Use this reference to learn Zuora Payments terms.
Zuora Payments products, add-ons and providers
- Zuora Payments
-
Zuora Payments is an end-to-end payment solution that helps you collect payments faster through prebuilt payment gateway integrations, automated payment processing, and intelligent recurring collection optimization.
- Modernized Zuora Payments
-
A paid Zuora Payments SKU that provides advanced payment capabilities, including payment service provider (PSP) connections, routing, customizable checkout, and Payments Insights.
- Bank Account Verification
-
An add-on SKU for Zuora Payments that verifies customers' ACH bank accounts and optionally checks real-time account balances during payment setup and processing. It helps reduce payment failures, improve security and compliance, and streamline ACH payment collection.
- Zuora Fraud Protection
-
An add-on SKU that evaluates payment transactions in real time to detect and prevent fraudulent activity before authorization. It uses identity intelligence, device fingerprinting, behavioral analytics, and transaction context to help reduce fraud losses and chargebacks while minimizing false declines.
- Configurable Payment Retry
-
An add-on SKU for Zuora Payments that automatically retries failed card payments using configurable business rules or AI-driven retry logic. It enables merchants to optimize payment recovery by defining retry strategies based on customer segments, gateway response codes, and other payment attributes, helping increase successful collections while reducing unnecessary retry attempts.
- Payment service provider (PSP)
-
Note:
This term is only applicable to Modernized Zuora Payments.
A third-party payment platform that enables merchants to accept and manage payments. A PSP typically provides payment gateway services along with additional capabilities such as payment processing, routing, tokenization, fraud prevention, reporting, and support for multiple payment methods. Modernized Zuora Payments connects to supported PSPs to provide these advanced payment capabilities.
- Payment gateway
-
A service that securely transmits payment information between a merchant, financial institutions, and payment networks to authorize and process payment transactions. In Zuora Payments, payment gateways are integrated to process customer payments through supported gateway providers.
- Payment gateway integration
-
A configured connection between Zuora Payments and a supported payment gateway. A payment gateway integration stores the credentials and configuration required for Zuora to communicate with the gateway and process payment transactions.
Payment methods and lifecycle
- Non-referenced refund
-
A refund that is processed without referencing a specific original payment transaction. Non-referenced refunds are supported only by certain payment gateways and payment methods, and are typically used when the original payment transaction is unavailable or cannot be referenced by the payment gateway.
- Payment method
-
A customer payment instrument used to process payments, such as a credit card, debit card, bank account, digital wallet, or local payment method. In Zuora Payments, supported payment methods depend on the configured payment gateway or payment service provider (PSP).
- Payment Method Updater (PMU)
-
A Zuora Payments capability that automatically updates stored credit card information through supported account updater services to help reduce payment failures.
- Card Account Updater (CAU)
-
Note:
This term is only applicable to Modernized Zuora Payments.
Modernized Zuora Payments capability that asynchronously refreshes stored card details when issuers replace or update them, reducing recurring-payment failures.
- Enrolled payment method
-
A payment method saved for recurring payments, renewals, retries, or returning-customer checkout.
- Non-enrolled payment method
-
A one-time payment method that is not saved for reuse.
- Payment run
-
A batch process that automatically collects payments for posted invoices with outstanding balances from customer accounts that have Auto-Pay enabled. A payment run processes payments using electronic payment methods, such as credit cards and ACH, and can be configured to run on demand or on a recurring schedule.
- Refund
-
A transaction that returns funds from a merchant to a customer for a previously collected payment. In Zuora, refunds can be issued for full or partial payment amounts through supported payment gateways and payment methods, and the refund status is tracked as part of the payment lifecycle.
- Delayed capture
-
A payment processing workflow that authorizes a payment to verify that funds are available but postpones capturing the funds until a later time. Delayed capture enables merchants to reserve funds when an order is placed and capture the authorized amount when goods or services are ready to be fulfilled.
- Payments Insights
-
Note:
This term is only applicable to Modernized Zuora Payments.
Modernized Zuora Payments analytics capability for monitoring payment volume, approval rates, declines, retries, refunds, chargebacks, fraud, and 3DS performance.
Payment orchestration
- Payment orchestration
-
The process of managing how payment transactions are routed, retried, and processed across one or more payment service providers (PSPs) or payment gateways. In Zuora, payment orchestration helps merchants optimize payment success rates, improve resiliency, and simplify payment operations through capabilities such as payment retry and gateway routing.
- Routing rules
-
A configurable rule that determines which payment service provider (PSP) or payment gateway processes a payment transaction based on specified conditions, such as payment method, currency, country, or transaction attributes. In Modernized Zuora Payments, routing rules enable merchants to optimize payment processing by directing transactions to the most appropriate PSP.
- Smart routing
-
Note:
This term is only applicable to Modernized Zuora Payments.
A routing strategy that automatically selects the most appropriate PSP for each payment transaction based on configured optimization goals and real-time transaction conditions. Smart routing helps improve payment performance by optimizing for factors such as authorization success rates, processing costs, and latency across supported PSP connections.
- Gateway reconciliation
-
The process of verifying that payment and refund transactions recorded in Zuora match the corresponding transactions reported by payment gateways or financial institutions. Payment reconciliation helps identify and resolve discrepancies, ensuring that payment records, settlements, and refunds are accurate and complete.
Checkout and hosted payment experiences
- Checkout
-
The customer-facing payment experience where customers enter and submit payment information to complete a transaction. In Modernized Zuora Payments, the Checkout component enables merchants to configure the appearance, available payment methods, and payment method conditions to deliver a customized payment experience.
- Hosted payment form / Hosted payment page
-
A hosted payment form (HPF) or a hosted payment page (HPP) is a web page hosted entirely on a third-party payment processor's secure servers where end-customers enter sensitive payment details to complete a transaction. In most cases, these two terms are interchangable.
In Zuora Payments, Payment Pages 2.0 is the feature that allows you to manage hosted payment pages, and Payment Form is the feature that allows you to create and manage payment forms.
If you have upgraded to Modernized Zuora Payments, you can use the Checkout Builder to build hosted payment forms that facilitates more modern checkout experience.
Customer- and merchant-initiated payments
- Customer-Initiated Transaction (CIT)
-
A payment transaction that is initiated by the customer while they are actively participating in the payment process. A CIT typically occurs when a customer enters or selects a payment method to make a payment or authorize the storage of payment credentials for future use. A CIT can establish the customer consent required for subsequent merchant-initiated transactions (MITs).
- Merchant-Initiated Transaction (MIT)
-
A payment transaction that is initiated by the merchant without the customer's active participation, based on the customer's prior consent to use stored payment credentials. MITs are commonly used for recurring billing, automatic invoice collection, installment payments, and other scheduled or agreed-upon payments.
- Stored credential profile
-
A record associated with a payment method that represents the customer's consent to use stored payment credentials for future transactions. In Zuora, a stored credential profile contains information required to support stored credential transactions, such as its status, type, consent agreement details, and, when available, the network transaction ID (NTI).
- Stored credential transaction
-
A payment transaction that uses payment credentials previously stored with the customer's consent. Zuora supports stored credential transactions for supported payment methods and payment gateways by identifying whether a transaction uses stored credentials, helping merchants comply with payment network requirements and improve authorization approval rates.
Payment security and fraud prevention
- 3-D Secure (3DS)
-
An authentication protocol that verifies a cardholder's identity during online card payments to help reduce fraud. Zuora Payments supports 3-D Secure through compatible payment service providers (PSPs) and gateways to help merchants authenticate customers before payment authorization.
- 3-D Secure 2.0 (3DS2)
-
The latest version of the 3-D Secure protocol. It supports risk-based authentication, improved user experiences across web and mobile channels, and the exchange of additional transaction data to reduce friction while helping prevent fraud.
- Network token
-
A 16-digit surrogate card number issued by a card network, such as Visa, Mastercard, American Express, or Discover, that securely represents a customer's primary account number (PAN). In Zuora, a network token is provisioned after a successful payment validation or transaction and can be used to process recurring and stored-credential payments across supported payment gateways without exposing the underlying card number.
- Network tokenization
-
A payment security capability that replaces a card's primary account number (PAN) with a network token issued by the card network. In Zuora, network tokenization enables recurring and stored-credential payments to use network tokens instead of raw card numbers or gateway-specific payment method identifiers, improving security, authorization success rates, and portability across supported payment gateways.
- Vault token
-
A secure Zuora token representing a stored payment method without exposing the underlying card data.
- Vaulted token
-
A token created when a payment method is enrolled and stored for future payments.
- Token Requestor Identifier (TRID)
-
An identifier used in network-token provisioning; merchants can retain an existing TRID when migrating tokens to Zuora.
- 3DS provider
-
A service that performs 3-D Secure authentication, either through a PSP or independently in a PSP-agnostic route.
- Fraud provider
-
A connected service that screens transactions and returns fraud decisions.
- Route condition
-
Criteria that determine when a payment route applies, such as country, currency, amount, payment method, or payment origin.
- Published route
-
A payment-processing route made active for a payment method; required before that method can be enabled in Checkout
Payment events and synchronization
- Webhook
-
An HTTP callback that automatically sends payment-related event notifications from Zuora to an external application when specified events occur. Webhooks can notify downstream systems of events such as successful payments, failed payments, refunds, and other payment lifecycle updates, enabling automated workflows and near real-time synchronization.