Welcome to Zuora Product Documentation

Explore our rich library of product information

Network Tokens with Checkout.com for Card Payments

Use network tokens with Checkout.com to process eligible Visa and Mastercard card payments in Zuora, reducing reliance on raw card numbers while preserving existing payment flows through prioritized credential selection and fallback behavior.

Zuora supports network tokens for eligible Visa and Mastercard card payments processed through the Checkout.com gateway. When an eligible network token is available, Zuora uses the network token instead of the underlying card number for supported Payment and Authorize transactions.

Network tokenization helps reduce reliance on raw card numbers for supported card payments. For Checkout.com, this support applies to standard credit card payment flows for customer-initiated and merchant-initiated transactions.

Apple Pay and Google Pay use their own payment flows and are not part of the standard card-processing priority described in this article.

To use network tokens, ensure the following prerequisites are met:

  • Your tenant has the Checkout.com gateway integration enabled.
  • Network tokenization is enabled for your tenant.
  • Network token provisioning is configured in Credential Management with the required Worldpay profile credentials.
  • The payment method has an active provisioned network token.
  • If you plan to process merchant-initiated transactions, the payment method is configured with the correct stored credential profile.

Supported card brands

Checkout.com network token support is available for Visa and Mastercard card payments.

If the card brand is not supported for Checkout.com network token processing, Zuora continues to use the standard Checkout.com card-processing path.

Supported transactions

This feature supports the following transaction types for eligible card payments:

  • Customer-initiated transactions

  • Merchant-initiated recurring transactions

  • Merchant-initiated unscheduled transactions, when the required stored credential conditions are met

  • Payment operations

  • Authorize operations

How Zuora chooses the payment credential

For standard credit card payments processed through Checkout.com, Zuora uses the following priority order:

  1. Network token

  2. Gateway payment method identifier

  3. Primary account number (PAN)

If a usable network token is not available, Zuora falls back to the existing Checkout.com payment flow.

Customer-initiated transactions

For customer-initiated transactions, Zuora can send the network token together with customer-authentication data, such as a cryptogram and ECI, when those values are available for the transaction.

This support applies to supported Checkout.com card payment flows that go through Zuora payment processing, including API-based payment flows and hosted payment collection flows.

Merchant-initiated transactions

For merchant-initiated transactions, Zuora can use a stored network token for eligible recurring and unscheduled payment flows.

For recurring merchant-initiated transactions, if a previous payment reference is available, Zuora uses it for transaction chaining. If a previous payment reference is not yet available, the first recurring transaction can still be processed, and the returned reference can be used for later recurring transactions.

For unscheduled merchant-initiated transactions, all of the following conditions must be met:

  • The transaction is merchant initiated

  • The transaction type is Unscheduled

  • The payment method is configured with the correct stored credential profile

  • A previous payment reference is available

If the stored credential profile does not match the transaction type, the request can fail.

How payment methods become eligible

For Checkout.com card payments, network token provisioning applies to supported card payment methods created through Zuora payment flows, including APIs and hosted payment collection flows.

For existing payment methods, a network token is provisioned after a successful transaction. For new payment methods, the network token is provisioned after the payment method is validated or authorized and is then used for later transactions.

If no network token is available

If no supported network token is available for a card payment, Zuora continues to use the existing Checkout.com flow. Depending on what is available for the payment method, Zuora uses either the gateway payment method identifier or the PAN.

This fallback behavior helps preserve compatibility with existing Checkout.com payment flows.

Considerations

Keep the following points in mind:

  • This feature supports only Visa and Mastercard card payments for Checkout.com.

  • Apple Pay and Google Pay use separate payment flows and are not covered by the standard credit card priority described in this article.

  • Merchant-initiated transactions can fail if the required previous payment reference is missing for flows that require it.

  • Suspended or revoked network tokens are not used for payment processing.

Supported card brands

Checkout.com network token support is available for Visa and Mastercard card payments.

If the card brand is not supported for Checkout.com network token processing, Zuora continues to use the standard Checkout.com card-processing path.

Supported transactions

This feature supports the following transaction types for eligible card payments:

  • Customer-initiated transactions
  • Merchant-initiated recurring transactions
  • Merchant-initiated unscheduled transactions, when the required stored credential conditions are met
  • Payment operations
  • Authorize operations

How Zuora chooses the payment credential

For standard credit card payments processed through Checkout.com, Zuora uses the following priority order:

  1. Network token
  2. Gateway payment method identifier
  3. Primary account number (PAN)

If a usable network token is not available, Zuora falls back to the existing Checkout.com payment flow.

Customer-initiated transactions

For customer-initiated transactions, Zuora can send the network token together with customer-authentication data, such as a cryptogram and ECI, when those values are available for the transaction.

This support applies to supported Checkout.com card payment flows that go through Zuora payment processing, including API-based payment flows and hosted payment collection flows.

Merchant-initiated transactions

For merchant-initiated transactions, Zuora can use a stored network token for eligible recurring and unscheduled payment flows.

For recurring merchant-initiated transactions, if a previous payment reference is available, Zuora uses it for transaction chaining. If a previous payment reference is not yet available, the first recurring transaction can still be processed, and the returned reference can be used for later recurring transactions.

For unscheduled merchant-initiated transactions, all of the following conditions must be met:

  • The transaction is merchant initiated
  • The transaction type is Unscheduled
  • The payment method is configured with the correct stored credential profile
  • A previous payment reference is available

If the stored credential profile does not match the transaction type, the request can fail.

How payment methods become eligible

For Checkout.com card payments, network token provisioning applies to supported card payment methods created through Zuora payment flows, including APIs and hosted payment collection flows.

For existing payment methods, a network token is provisioned after a successful transaction. For new payment methods, the network token is provisioned after the payment method is validated or authorized and is then used for later transactions.

If network tokens are not available

If no supported network token is available for a card payment, Zuora continues to use the existing Checkout.com flow. Depending on what is available for the payment method, Zuora uses either the gateway payment method identifier or the PAN.

This fallback behavior helps preserve compatibility with existing Checkout.com payment flows.

Considerations

  • This feature supports only Visa and Mastercard card payments for Checkout.com.
  • Apple Pay and Google Pay use separate payment flows and are not covered by the standard credit card priority described in this article.
  • Merchant-initiated transactions can fail if the required previous payment reference is missing for flows that require it.
  • Suspended or revoked network tokens are not used for payment processing.