Resources
Blog
7 Minute read

Mastercard TLID mandate: what the repeat payments rule changes

Anthony Aslan
Ryft

In this article, we explain Mastercard’s TLID mandate, the key dates, and expected changes.

Get fresh insights, monthly

Stay up to date with our latest news and insights.

Since 23 October 2026, Mastercard expects merchant-initiated payments on a stored card to carry a Transaction Link Identifier (TLID). The TLID comes from the first card-on-file payment that set up the agreement. It looks like a minor data field, but it changes how subscriptions, instalments and top-ups link back to that agreement.

If you process with Ryft, there is nothing for you to build. We store the TLID the acquirer returns on the initial payment and send it on later merchant-initiated transactions (MITs), including cross-acquirer ones. The rest of this post explains the change, and what needs to be considered.

‍

What changed on 23 October 2026

The TLID is a 22-character reference generated by Mastercard and carried in data element DE 105. It is case-sensitive and can contain letters, digits, hyphens and underscores. Some publications quote 36 characters, but the provider documentation we found says 22. Confirm with your acquirer before fixing a database schema.

Merchants don't create it. It comes back in the authorisation response to the original customer-initiated transaction (CIT), or to a zero-amount account status inquiry, and has to be stored. It is then sent on later related MITs, such as a renewal months after sign-up. Always use the TLID from the CIT or verification that set up the agreement, not the one from the latest renewal.

It applies to Mastercard transactions only, including co-branded debit routed over the Mastercard network, and the mandate is global.

‍

Mastercard TLID mandate key dates

Timeline, 2025 to 2027

Date What happens
17 Oct 2025 Acquirers must carry the TLID in each lifecycle message that follows the original authorisation
2 Jun 2026 Merchants and acquirers must start retaining the TLID returned on CITs where a card is stored for future payments
23 Oct 2026 For MITs on or after this date, acquirers must include the TLID retained from the original CIT, where available
1 Dec 2026 Comply-by date for the Data Integrity Monitoring Program edit
31 Jan 2027 Assessments reported to begin, aimed at acquirers. Some sources say these cover lifecycle linking only

‍

This is separate from Mastercard’s subscription standards on receipts, trial reminders and cancellation information, in force since 22 September 2022. Those govern what you tell the cardholder. The TLID governs how payments are linked in the data.

‍

Why Mastercard introduced the TLID

The TLID supplements the legacy linking fields: the Banknet Reference Number, Trace ID and Switch Serial Number. Some providers say it replaces them, but Mastercard hasn't set a retirement date and has said it will give advance notice. Until then the old identifiers are still sent alongside it.

The problem it addresses is ambiguity. Merchants had to decide whether an MIT should reference the prior transaction or the original one, and links could break when a credential switched between PAN and network token. One acquirer also says Trace IDs were generated by the acquirer and could be duplicated. Other providers describe the Trace ID as a network reference, so treat that as one provider's view, not Mastercard's.

The practical payoff is in disputes. If a customer disputes a later MIT, the TLID helps you find the first payment and the evidence behind it. The same acquirer says it can locate the original authentication message, and reports fewer false declines on later payments when the first carried strong authentication data. That is its own observation, not a Mastercard figure. Industry commentary also lists continuity across PSPs among the aims.

‍

What the TLID mandate affects

Legacy stored credentials

Merchants and acquirers were only required to start retaining the TLID from CITs on 2 June 2026, so card-on-file agreements set up before then usually have no stored TLID to send. The usual fallback is to process your next routine MIT, take the TLID from its authorisation response, save it and send it on later MITs. Stripe, for example, sends the TLID from the earliest authorised MIT after 2 June for older credentials.

Alternatives include a zero-value account status inquiry for a fresh TLID, or a new authenticated CIT as a last resort. Which route is expected depends on your acquirer.

New card setups

Adding or re-verifying a card is a new CIT. It generates a new TLID, which then applies to later MITs on that setup.

Multiple PSPs, gateways and orchestrators

If cards are saved outside your PSP, in an orchestrator or a third-party vault, someone has to capture, store and send the TLID from the original CIT. The field can be dropped or truncated at any gateway, orchestration layer or sub-processor, and support varies between them, so check every hop.

Several agreements on one card

Store the TLID per card and per agreement, and pass an agreement ID. Otherwise the wrong TLID could be applied.

Platforms and marketplaces

From our perspective, if you charge on behalf of sub-merchants, the TLID has to stay with the right agreement through onboarding changes, migrations and PSP switches. On Ryft, that sits with us rather than with the platform.

Enforcement

Mastercard has confirmed that no network logic declines a transaction for a missing or incorrect TLID. Some providers describe 23 October as the start of compliance monitoring rather than a hard processing requirement.

The signals on consequences point in different directions. Some providers warn of higher issuer decline rates for merchants that don't pass the TLID. Others warn of scheme fines, or higher declines where a different provider processed the original CIT. Watch your own decline data rather than relying on any one of these.

Assessments are aimed at acquirers, who decide whether to push the requirement down to merchants. Several providers report acquirer assessments from 31 January 2027, with monthly amounts under the Data Integrity Monitoring Program, but we haven’t found this in a Mastercard document. Note that 23 October is when the MIT requirement took effect, not when non-compliance is assessed. Mastercard hasn’t confirmed an assessment date specifically for linking MITs to their original CIT.

‍

What Ryft merchants should do now

If you process with Ryft, you don't need to do anything. Ryft stores the TLID the acquirer returns on the initial payment and sends it on later MITs, including cross-acquirer ones. There is no field to add and nothing to store on your side.

‍

Anthony Aslan
Ryft

Frequently asked questions

The TLID is a Mastercard reference that links repeat payments back to the first payment. Mastercard generates it in the authorisation response to a customer-initiated transaction, and it is usually 22 characters long. Merchants store it and send it on later merchant-initiated payments on that card, such as subscription renewals and instalments.

The main merchant-facing date was 23 October 2026, when the rule began applying to merchant-initiated transactions. From then, acquirers must send the TLID retained from the original customer-initiated transaction on each related payment, where available. Data integrity monitoring has a comply-by date of 1 December 2026, with assessments reported from 31 January 2027.

Mastercard has reportedly confirmed that no network logic declines a payment for a missing TLID. Some providers still warn of higher issuer decline rates for merchants that don’t pass it on. Check how your acquirer, gateway and payment processor each handle the TLID, and watch your own Mastercard decline data closely.

More Blogs

Blog

Best payment providers for service apps in 2026

In this guide, we compare the best payment providers for iOS and Android service apps that collect from customers and pay out to providers in 2026.
Read more
Blog

The cost of processing payments for airlines and travel businesses in 2026

In this guide, we explain what drives payment processing costs for airlines and travel businesses in 2026, using IATA's latest data.
Read more
Blog

PayFac as a service for SaaS platforms: a 2026 guide

In this guide, we explain how PayFac as a service works for SaaS platforms, when it is worth it, and what to check before choosing a provider.
Read more

Let's talk about payments

Our payment experts are here to talk through your requirements and set you up for success.

Contact us