In June 2024, Mastercard introduced the Transaction Link Identifier (TLID) – a new, scheme-generated reference that they intend to eventually replace the scheme ID (previous_payment_id) for tracking and linking transactions across the ecosystem.
Mastercard will expand their TLID use requirements later this year to cover economically related transactions such as recurring payments and instalments.
Our API now returns and accepts the TLID in the processing.scheme_transaction_link_id field, and we’ve published updated docs on recurring payments with stored card details with information about how we process the TLID..
Key dates
- October 2025: Mastercard introduced the TLID for standard lifecycle messages such as chargebacks, reversals, and captures. We already handle the TLID for these transactions
- June 2, 2026: Mastercard recommends that merchants store the TLID for all cardholder-initiated transactions
- October 23, 2026: Mastercard will require the TLID for economically related transactions (Merchant Initiated Transactions such as recurring payments and instalments)
How to prepare
For transactions processed with Checkout.com
For Mastercard transactions where you processed the first Customer-Initiated Transaction (CIT) and following Merchant-Initiated Transaction (MIT) with Checkout.com, you can continue to provide the previous_payment_id.
We will resolve the TLID on your behalf, so nothing needs to change with your integration.
If you do not provide a previous_payment_id, we automatically try to retrieve the TLID from the first CIT in the payment series. We do not recommend that you use this fallback mechanism as your primary method of managing the TLID.
For transactions processed with other payment providers
If you process Mastercard MITs on Checkout.com where the initial CIT was processed through another provider (or vice versa), you must capture, store, and send the TLID for these transactions in addition to the previous_payment_id.
Our API accepts and returns the TLID in the processing.scheme_transaction_link_id field.
Some MITs originate from a historic CIT or Account Status Inquiry where the original TLID is not available. For these transactions, you should provide the TLID from an earlier MIT that was not disputed, dated within the last three months. Subsequently, you can use this TLID for all MITs.
FAQs
What is the Mastercard Transaction Link Identifier (TLID)?
The TLID is a new, unique reference generated by Mastercard. It is a universal identifier that links the first payment to all future actions like refunds, chargebacks, or recurring billing.
How does the TLID differ to the Trace ID/Scheme ID I already use?
While the Trace ID/Scheme ID is used for specific lifecycle events, the TLID is a more robust, globally unique identifier that will eventually become the main way Mastercard tracks a transaction’s entire history. For now, you will need to handle both.
Is the TLID mandate global?
Yes, this mandate applies to all regions.
Do other schemes plan to introduce a similar identifier to the TLID?
We’re not aware of any other schemes’ plans to introduce a similar identifier. If we become aware of this, we’ll let you know.
Where can I find the TLID in the API response?
This is in a new processing.scheme_transaction_link_id response field.
How can I provide the TLID for MITs in my API requests?
Use processing.scheme_transaction_link_id to provide the TLID in your requests.
Will Mastercard return a TLID for both PAN and Network Token transactions?
Yes.
Will Checkout.com return a TLID in the refund API response?
No. Checkout.com will manage the TLID for lifecycle transactions such as refunds and chargebacks.
What if I don't provide a TLID for an MIT after October 2026?
If another provider processed the initial CIT, transactions missing the required TLID may be subject to scheme fines from Mastercard or could experience higher decline rates from issuers.
What do I do for subscriptions that started years ago (before TLIDs existed)?
For "historic" transactions where no original TLID exists, you should use the TLID from the most recent successful recurring payment (non-disputed) that occurred within the last three months. Once you use that TLID, it becomes the reference for all future payments in that series.
How should I store the TLID?
The TLID is a 22-character alphanumeric string. You should ensure your database schema for stored credentials can accommodate this new field length and format.
Do I need to update the TLID if a customer updates their card details?
Any event that requires a new customer-authenticated card setup (like adding a new card or re-verifying an existing one) is a new CIT. This CIT will generate a new TLID in the authorization response.
The next TLID must be used for all future Merchant-Initiated Transactions (MITs) associated with that specific card setup.
What should I be doing right now to prepare for the TLID?
You should begin storing the TLID for all CITs. If you use multiple payment gateways, ask your other providers when they will start surfacing the TLID.