Mastercard TLID Requirements for Recurring Billing

For businesses that keep cards on file and charge them later, Mastercard is changing its requirements starting October 23, 2026.

It involves what has to be included with those payments, and it’s called the Transaction Link Identifier (TLID for short).

There’s been a fair amount of coverage on this industry-wide since Mastercard first announced it. But almost all of it comes from gateways writing for developers, and practically nothing so far speaks to the actual businesses running recurring billing through a software platform. 

While the technical handling of TLID isn’t really a merchant issue, it’s still something you should be aware of if you run card-on-file payments. As there could be some cost changes around the corner if you’re not running those cards up to Mastercard’s new standards. 

What the Mastercard Transaction Link Identifier Is

The TLID is a 22-character ID code that Mastercard generates on its own and then attaches to the first message of a transaction. This is actually something that Mastercard first introduced back in 2024.

From there, that same ID follows everything tied to the original payment, including:

• Captures
• Refunds
• Chargebacks
• Renewal billing

Merchants have already had a way to link these transactions through something called a Trace ID or network transaction reference. Those aren’t going away, and the existing linking fields are still required alongside the TLID.

Though Mastercard plans to phase out the Trace ID over time. And during the transition, many recurring billing and card on-file setups will use both. 

Does the New Mastercard TLID Requirement Apply to Your Business?

Transaction Link Identifiers are aimed at businesses storing a customer’s card on file and charging it later. But it’s only required for merchant-initiated Mastercard transactions using on-file credentials.

For example, if a customer logs into their profile and checks out using a saved card, the merchant isn’t initiating that payment. 

Whereas categories like gym memberships, food subscription boxes, storage unit rentals, and software subscriptions would all fall under the new TLID requirements. 

The billing schedule doesn’t matter. Both fixed monthly billing and irregular one-off charges to a stored card are both covered by TLID, including:

• Software subscription billed at $20 on the 15th of every month.
• Vet clinic wellness plan split into 12 monthly payments.
• Dry cleaner holding a card on file, going two months without a charge, then bills $90 for a pickup and $24 the following week.
• Lawn care companies charging the stored card after each visit at varying rates for different services rendered.

In every one of these cases, whatever system running the card also has to flag the payment as merchant-initiated for the TLID to travel with it.

If you only take one-time payments and never store cards on file for future charges, this mandate isn’t aimed at you.

But if you take the first payment in person and then bill that same card later for a membership or payment plan, you’ll need to ask your provider how those subsequent charges get handled, as TLID will likely apply. 

TLID Timeline for Recurring and Card-on-File Payments

Mastercard has been rolling this initiative out in phases. Here are the dates that matter most to a recurring billing merchant:

• June 2, 2026: Retention phase began. Processors and merchants were expected to start keeping the TLID from CNP transactions when a card gets saved for future use.
• October 23, 2026: Stored TLID has to be sent with every related merchant-initiated authorization.
• December 1, 2026: Formal “comply-by” date under Mastercard’s Data Integrity Monitoring.
• January 31, 2027: Assessments start.

In simple terms, October 23rd is when the rule takes effect. 

From that point on, any merchant-initiated Mastercard payment from an on-file card is supposed to carry the TLID from the original transaction.

For most businesses, nothing visible happens on the effective date. If your provider has it all handled for you, then you won’t even notice anything. But if not, Mastercard says its network won’t decline a charge over a missing TLID, and no fines are scheduled until January 31, 2027.

The real pressure between then and now falls on payment processors and gateway providers. That’s why it’s worth confirming your setup now before potential assessments start trickling down to your statements in early 2027.

Your Provider is the One Who Has to Handle This

The majority of small and midsize recurring billers won’t directly touch any of this stuff, as Mastercard puts formal obligation on the acquirer. 

But the TLID also has to be saved by whichever company stores the card. And that role depends on your setup:

• An integrated platform that also processes your payments should handle everything end-to-end.
• Software that stores cards but sends charges to a separate processor will share that job with the processor.
• Cards kept in your processor’s virtual terminal or gateway (like Authorize.net) leave this responsibility to the gateway or processor.

Based on my research, all of the big processors say they have it covered.

Adyen has told merchants using its own tokenization that no action is required. Checkout.com says the same thing when it handles both the first payment and future charges. 

Where I’d be worried or at least have questions is in any setup where the card vault and processor aren’t the same company. Or in scenarios like:

• You switched processors in the past few years
• You migrated stored cards from one processor to another
• You’re using a smaller payment platform running their own card storage

Also, in any case where there’s a backlog of stored cards saved before any of this started, those original transactions won’t have a TLID to pull.

In those instances, the solution is going to be processor-dependent. You can likely either obtain a TLID from a successful, undisputed recurring payment within the past few months. Or run the next renewal with the existing network reference and then save that TLID for future payments.

But again, you need to check with whoever stores your cards and processes the payments to determine the fix here. 

How Much Does Mastercard’s TLID Cost?

You won’t see any “TLID fee” line items on your credit card processing statement.

Enforcement runs through Mastercard’s Data Integrity Program, and those assessment charges start on January 31, 2027. They’re billed to acquiring banks, and how your processor ultimately passes them to you (and at what price) comes down to your agreement.

I’ve watched processes pass through network penalties for years in different ways. Sometimes at cost (the way it should be), and sometimes with extra padding.

Mastercard has also been leaning on fees to push recurring billing merchants toward cleaner data for a while now. Their Credential Continuity Program Fee already charges $0.09 per recurring transaction running on outdated credentials. And the Transaction Processing Excellence Fees hit merchants for sloppy authorization patterns.

TLID fits that same pattern. 

One more point on potential costs: While Mastercard has confirmed its network isn’t going to decline transactions over missing TLIDs, it’s possible that the issuer could decline them. Your renewals probably won’t start bouncing overnight, but if that eventually happens on the issuer side, there will be extra decline-related costs to think about.

The Chargeback Upside for Subscription Businesses

I think it’s worth talking about a real benefit buried underneath all this. 

One of the most challenging parts of a recurring billing dispute is showing that the renewal belongs to the same payment relationship that a customer set up in the first place. And the TLID gives processors, acquirers, and issuers a true network-level way to make that connection. 

It’s not going to win any chargebacks on its own.

You’ll still need signup records, recurring terms, cancellation policies, and proof your service was actually delivered. But what the TLID provides is a cleaner trail of the payment itself.

If recurring billing disputes are already a headache for your business, you can read my guide on how to fight and win recurring billing chargebacks to tackle this with actionable steps. 

Questions to Ask Your Software About TLID to Ensure Compliance

Rather than waiting until next year to see if you’re hit with additional charges, I’d recommend sending a short email to your processor or payment software support team to clear things up about your setup.

Ask them:

• Are you saving the Mastercard TLID when a customer stores a card?
• Will renewals include it by October 23rd?
• How are cards stored before June 2026 being handled?
• If Mastercard assesses data integrity fees, do those get passed to me?

Confident specific answers are a good sign. If they’re vague or can’t answer directly, it’s worth a follow-up conversation. 

And if you’re unsure whether certain network penalties or assessments are being passed through properly come February 2027, our team here at MCC can audit your statements for free to see if your processor is padding anything.