Without Network Tokenization

If the tenant configures multiple gateways, such as Gateway A and Gateway B:

• A successful PAN‑based transaction with Gateway A:
  • Produces a Gateway‑A‑specific payment method ID.
• A successful PAN‑based transaction with Gateway B:
  • Produces a Gateway‑B‑specific payment method ID.

• Zuora may need to store multiple gateway IDs, one per configured gateway.
• A gateway token from Gateway A cannot be reused at Gateway B.
• To obtain a token for Gateway B, Zuora must send the PAN to Gateway B and let Gateway B generate its own identifier.

With Network Tokenization

With network tokenization enabled and a token successfully provisioned:

With network tokenization enabled and a token successfully provisioned:

• Zuora obtains a network token directly from the card network via Worldpay.
• That network token is independent of any single gateway:
  • It can be used with Gateway A and Gateway B, as long as those gateways are supported for network tokenization in Zuora.
• When Zuora sends the network token (for example, 1762) to a supported gateway:
  • The gateway forwards it to the card network (for example, Visa).
  • The network resolves the token back to the original card (for example, 6217) and calls the issuing bank to process the transaction.

As a result:

• The network token becomes a gateway‑agnostic identifier, within the set of gateways where Zuora supports network tokens.
• You do not need a separate gateway token for each gateway if the transaction can be processed via network tokens.

Gateway support and limitations

If a customer uses a gateway that Zuora does not support network tokenization:

• Zuora does not send the network token to that gateway.
• The integration continues to use:
  • The PAN, or
  • The gateway’s own payment method ID.