Stripe v2 Mastercard Transaction Link Identifier
Stripe v2 supports Mastercard Transaction Link Identifier (TLID) processing for eligible stored credential payment transactions.
Stripe v2 supports the Stored Credential Transactions framework for eligible payment methods and transaction flows.
For supported Mastercard stored credential transactions, Zuora can store and reuse the Mastercard Transaction Link Identifier (TLID).
When Stripe returns a TLID during a qualifying Mastercard transaction, Zuora stores it with the stored credential data.
When Zuora processes a subsequent eligible Mastercard merchant-initiated transaction (MIT), it retrieves the stored TLID and includes it in the payment request that it sends to Stripe.
This process allows the later transaction to reference the original Mastercard transaction when the gateway and card network require the reference.
The TLID complements the Network Transaction ID (NTI). These identifiers can have separate roles in the payment request. The exact request mapping depends on the Stripe v2 implementation and transaction flow.
Supported transaction behavior
TLID handling applies to supported Mastercard stored credential flows, including eligible recurring and other merchant-initiated payments.
The initial customer-initiated transaction (CIT) establishes the stored credential relationship and provides the value that Zuora can reuse for later related transactions.
If a later eligible transaction returns a new TLID, Zuora can update the stored value for subsequent related transactions, subject to the Stripe v2 response behavior.
Configuration requirements
No TLID-specific configuration is required in Zuora.
Configure Stripe v2 and stored credential processing according to the requirements for the integration.
Limitations
TLID handling depends on the Stripe v2 response and the supported Mastercard stored credential flow.
If Stripe does not return a TLID, Zuora cannot store or send one for that transaction.
The TLID does not replace the NTI. Do not assume that one identifier can replace the other unless the payment flow and gateway request mapping explicitly support that use.
TLID availability through 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 corresponding documentation confirms it.