In June 2024, Mastercard introduced the Transaction Link Identifier (TLID) – a new, scheme-generated reference that Mastercard intends to replace the scheme ID (previous_payment_id) for tracking and linking transactions across the ecosystem.
Mastercard will expand the requirements for the use of the TLID later this year to cover economically related transactions such as recurring payments and installments.
We began returning the TLID in our API responses on May 28, and will update our docs and API reference shortly.
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 begin storing the TLID for all cardholder-initiated transactions
- October 23, 2026: Merchants must provide the TLID for economically related transactions (merchant-initiated transactions including recurring payments and instalments)
Note: There is no impact if you don't supply the TLID before October 23rd.
How to prepare
For transactions where both the Customer-Initiated Transaction (CIT) and subsequent Merchant-Initiated Transaction (MIT) were processed with Checkout.com, we recommend supplying the TLID from October 23rd onwards.
If you don't provide a TLID, Checkout.com will automatically attempt to retrieve the TLID linked to the previous_payment_id, and apply relevant exemptions if this is missing. However, we do not recommend that you use this fallback mechanism as your primary method of managing the TLID.
If you process any Mastercard MIT 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 existing previous_payment_id.
We return the TLID in our API response as processing.scheme_transaction_link_id.
Note: We have updated this field name since our previous communication to better align with our API naming conventions.
Managing the TLID for historic transactions
Some recurring, subscription, installment, BNPL, or MITs originate from a historic Cardholder Initiated Transaction or Account Status Inquiry where the original TLID is not available.
For these transactions, you should provide the TLID from a previous recurring, subscription, installment, BNPL, or MIT that was not disputed, dated within the last three months.
Subsequently, you can use this TLID for all future recurring, subscription, installment, BNPL, or MITs.
Next steps
We will share our updated documentation in the next communication on this mandate. Please review this and ensure you have these changes planned in your roadmap before the June 2026 deadline.
If you have any questions about your data quality or status, please contact your Account Manager or raise a support request.
FAQs
What is the Mastercard Transaction Link Identifier (TLID)?
The TLID is a new, unique reference generated by Mastercard. It is designed to act as a universal identifier that links an initial payment to all subsequent related 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 often 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 where Mastercard is accepted.
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.
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.
How can I submit the TLID for subsequent MITs in my API requests?
We're currently scoping this out and will let you know in our next communication.
What if I don't provide a TLID for an MIT after October 2026?
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 Customer-Initiated Transaction (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 review your internal database to see if you can store an additional 22-character string against your customer payment profiles. If you use multiple payment gateways, begin asking your other providers when they will start surfacing the TLID.