Ecommerce platforms and AI

Mastercard TLID now required on stored-card merchant charges

Since October 23, 2026, Mastercard expects the Transaction Link Identifier from the original checkout to travel with every later merchant-initiated charge on a stored card. Subscription, replenishment and B2B card-on-file billing are in scope. Most processors handle it for their own tokens, merchants with their own vault must do the work, and processors disagree on the enforcement dates.

In short: Since October 23, 2026, Mastercard expects the Transaction Link Identifier from the original checkout on every later merchant-initiated charge to a stored card, such as subscriptions. Stripe, Adyen and Checkout.com handle it for their own tokens; merchants with their own card vault must store and send it. Processors give different enforcement dates.

Intelligize Digital 4 min readAll notes

Mastercard TLID now required on stored-card merchant charges

Key points

  • From June 2, 2026, processors had to retain the TLID from cardholder-initiated transactions that set up future card use.
  • From October 23, 2026, that TLID has to be sent with every later merchant-initiated transaction.
  • Stripe, Adyen tokenization and Checkout.com as sole acquirer handle the TLID for the merchant.
  • Checkout.com gives August 2027 as the comply-by date, while PayPal Braintree lists December 1, 2026.
On this page

What Mastercard changed and when

Mastercard now generates a Transaction Link Identifier (TLID) for each transaction. Stripe’s documentation describes it as an ID that links transactions across authorization and clearing messages, similar to the network transaction ID. For an online store, its job is to tie a later charge on a saved card back to the checkout where the shopper first saved it.

The rollout came in two steps. From June 2, 2026, processors had to retain TLIDs from cardholder-initiated transactions that set up future card use. From October 23, 2026, the TLID from that original transaction has to be sent with every later merchant-initiated transaction. Adyen’s notice gives the same two dates and calls October 23 the Requirement Enforcement Date.

The new ID runs alongside the existing ones. Stripe says network transaction IDs continue in parallel. Adyen tells merchants to keep sending the Trace ID as well, because Mastercard currently requires both and “Removing the Trace ID will result in compliance errors.”

Which stores this affects

The rule covers merchant-initiated transactions on stored Mastercard cards, and Checkout.com notes the ID is consistent across Mastercard acceptance brands, including Maestro. In ecommerce that usually means subscriptions and replenishment orders, B2B accounts where the card on file is charged when goods ship or an invoice falls due, and backorders charged after the original checkout. In Adyen’s API an MIT is a payment with shopperInteraction set to ContAuth and recurringProcessingModel set to Subscription or UnscheduledCardOnFile.

A store that only takes one-off card payments at checkout has no merchant-initiated charges, so it has nothing to send.

When the processor handles it for you

Who does the work depends on where the card token lives.

  • Stripe stores and returns TLIDs for all businesses and sends them on merchant-initiated transactions when the customer saved the card on Stripe. For cards saved before June 2, 2026, Stripe uses the TLID from the earliest authorized merchant-initiated transaction after that date. The value is returned at payment_method_details.card.transaction_link_id on the charge.
  • Adyen says merchants using Adyen tokenization need no action. Merchants with their own vault or a third-party token provider must read additionalData.transactionLinkId from the authorization response, store it with the token and send it with the Trace ID on every MIT.
  • Checkout.com says merchants using it as their only acquirer do not need to send the TLID, because Checkout.com stores it and looks it up for each relevant transaction.

The work lands on merchants with their own vault, a token service sitting in front of several processors, or a subscription or billing tool that stores network references itself. Stripe also notes that TLIDs “might need to be provided by users if Stripe does not have them available.” We would check that case first for any set of saved cards that was migrated in from another processor.

Enforcement dates differ by processor

Processors do not publish the same enforcement timeline. Checkout.com’s article, published November 10, 2026, gives August 2027 as Mastercard’s comply-by date and says “Additional fees for non-compliance will be applied from September 2027.” It adds that Mastercard “is not currently declining transactions for missing TLID.” The PayPal Braintree fall 2026 network update lists a comply-by date of December 1, 2026, with assessments beginning January 31, 2027. Adyen warns that if the TLID is missing on a transaction after June 2, 2026, the issuer may decline it.

The format descriptions differ too. Stripe describes a 22-character value, Checkout.com a 36-character string, and Adyen suggests a 22-character database field or larger. With that much variation, ask your acquirer in writing which dates, fees and field length apply to your merchant account.

Checkout.com estimates the implementation at about a week or less. We would run the change against a copy of the next subscription batch in the processor’s test environment, then confirm that the first live batch returns a populated TLID on every Mastercard charge.

What to do before the next billing run

5 checks
  • List every process that charges a saved card without the shopper present, including subscription apps, ERP-driven invoice billing and backorder capture scripts.
  • For each one, confirm whether the token lives with your processor or in a vault you control.
  • If you control the vault, add a column wide enough for 36 characters, store the TLID from each cardholder-initiated authorization and send it with the Trace ID on later charges.
  • For older tokens, Adyen’s method is to run the next recurring payment with the existing network reference, save the TLID that comes back and use it from then on. Checkout.com describes the same approach.
  • Keep the TLID with your order records. Checkout.com notes it is not PCI sensitive and helps with reconciliation, disputes and moving between acquirers.
Certifications

Certifications and partner programmes

Intelligize Digital is a registered partner of these platforms and hosts.

  • BigCommerce BigDev CertifiedBigCommerce Certified
  • BigCommerce Certified PartnerBigCommerce Certified
  • Liquid Storefronts for Theme Developers (Shopify Certified)Liquid Storefronts for Theme DevelopersShopify Certified
  • Headless at Shopify for Developers (Shopify Certified)Headless at Shopify for DevelopersShopify Certified
  • Shopify Foundations (Shopify Certified)Shopify FoundationsShopify Certified

Is this job still done by hand in your store?

Tell us the job and the systems it touches. An engineer reads every request, and we aim to reply within one business day.

We save what you type here so we can follow up if you get interrupted.
One file, up to 10 MB: PDF, Word, Excel, CSV, text, PNG or JPG.

An engineer replies within one business day.

What happens next

  1. An engineer replies We aim to reply within one business day, by email.
  2. A free 30-minute audit On a call with an engineer.
  3. A fixed quote Usually within 3 business days of the audit. Nothing is billed before you agree it.

Book a free audit. One form, one reply from an engineer.

Tell us what you are building or fixing. An engineer reads every request and replies within one business day, with a fixed scope, price and dates once we have talked.

Direct
[email protected]
Response time
Within one business day
Cost of asking
Nothing. The first 30-minute audit is free.

An engineer reads every request.