Nuvei Mastercard Transaction Link Identifier support
Nuvei returns a Mastercard Transaction Link Identifier (TLID) for supported stored credential transactions. Zuora stores it for eligible subsequent transactions.
Nuvei can return a Mastercard Transaction Link Identifier (TLID) for supported Mastercard stored credential transactions.
Zuora captures the TLID returned during a qualifying Mastercard cardholder-initiated transaction (CIT) and stores it with the stored credential data. Zuora can include the stored TLID in eligible subsequent Mastercard merchant-initiated transaction (MIT) requests, including recurring and unscheduled payments.
3DS2 and non-3DS2 transactions
TLID handling applies to supported Mastercard CITs processed through 3-D Secure 2.0 (3DS2) and non-3DS2 flows.
For a 3DS2 transaction, Zuora performs authentication through Nuvei. Authentication can use a frictionless flow or a challenge flow. After the CIT completes successfully, Zuora stores the TLID returned by Nuvei for eligible subsequent MITs.
For a non-3DS2 transaction, Zuora stores the TLID returned by Nuvei after the CIT completes successfully. Zuora can use the TLID in eligible subsequent Mastercard MITs.
TLID configuration
No TLID-specific configuration is required in Zuora.
Configure stored credential processing as described in the documentation for stored credentials, cardholder-initiated transactions, and merchant-initiated transactions.
To use stored credentials with Nuvei, activate the Tokenize payment method setting on the Nuvei gateway instance.
To ensure that network identifiers are returned and stored, activate Verify updated payment method when required by your payment flow.
Limitations
TLID handling depends on the Nuvei response and the supported Mastercard transaction flow.
If Nuvei does not return a TLID, Zuora cannot store or send one for that transaction.
TLID availability in the Zuora user interface, APIs, data sources, or exports depends on the supported stored credential data model. Do not rely on TLID availability through these interfaces unless the related documentation confirms it.