Mastercard TLID explained and what merchants need to do
Mastercard TLID links related payment activity. Merchants should preserve the original transaction reference, keep each payment’s own TLID separately, and verify storage, provider handoffs, and clearing. The Transaction Link ID 1240 clearing edit has an August 1, 2027 comply-by date and September 26, 2027 assessment start.
In this article
- What is Mastercard TLID
- Why Mastercard is introducing TLID
- How TLID works for subscriptions
- Messages within one payment lifecycle
- A later payment that references the original
- Which TLID dates should merchants track
- How TLID relates to the references you already store
- Who needs to change their integration
- Why TLID matters when you use multiple providers
- What merchants should do now
- 1 Map the fields on every route
- 2 Check storage with actual responses
- 3 Plan for older subscriptions
- 4 Test a payment across providers
- 5 Check clearing as well as authorization
- Acquirer implementation guidance
- Common TLID questions
- Can we generate a missing TLID ourselves
- Should we overwrite the original TLID after every renewal
- If our provider handles TLID automatically are we finished
- Start with one subscription
- Sources
Mastercard’s Transaction Link Identifier, or TLID, helps connect related payment activity across the payment chain. For merchants, the practical task is to receive it, store the right reference, and supply it when required.
That sounds like a small integration change. It becomes more interesting when a subscription renews through a different provider, or older customer records have no TLID.
This guide explains the identifier, the updated clearing dates, and the checks your payments team should make.
What is Mastercard TLID
A TLID is a 22-character identifier generated by Mastercard. It gives payment participants a consistent way to identify and link transaction activity. Mastercard’s technical release notes describe its format and purpose.
| TLID at a glance | What it means for your team |
|---|---|
| Generated by Mastercard | Receive the value through your provider |
| Exactly 22 characters | Allow the full value in storage and integrations |
| Letters, numbers, hyphens, and underscores | Preserve every character and its case |
| A reference for transaction activity | Keep its relationship to the original payment clear |
Think of it as a reference that helps systems connect the payment records that belong together. Your card credential identifies the payment method; the transaction reference helps preserve the payment history.
For later payments, use the original reference required by your provider. Keep each payment’s own TLID separately.
Why Mastercard is introducing TLID
A payment passes through several systems. The team investigating it needs to connect the original authorization with later processing activity.
Mastercard describes TLID as a globally unique reference designed for consistent transaction linking. Its October 2026 bulletin identifies traceability, dispute investigation, and operational research as intended benefits.1
For a merchant, that creates a useful operating goal: a payments analyst should be able to follow the relationship between records across systems.
Keep the underlying consent and billing agreement records too. A transaction reference is one part of that payment history.
How TLID works for subscriptions
Start with two common payment types:
- Cardholder-initiated transaction, or CIT: the customer initiates the payment, such as the first payment when signing up.
- Merchant-initiated transaction, or MIT: the merchant initiates a payment under an existing agreement, such as a scheduled renewal.
Now separate two relationships.
Messages within one payment lifecycle
Authorization is the issuer’s decision on a payment request. Capture requests financial completion of the authorized payment. Clearing exchanges financial transaction records between payment participants.
These stages belong to the payment’s lifecycle. Their messages need the appropriate links to the authorization.
A later payment that references the original
A subscription renewal starts another payment lifecycle. It references an earlier transaction and can receive its own TLID.
J.P. Morgan’s documentation provides a clear example. The MIT request sends the CIT’s TLID as originalTransactionLinkId. The response contains a new transactionLinkId for the MIT.
Original payment
Later renewal references A
A and B are illustrative labels. They are not valid TLIDs. The request-field example follows J.P. Morgan’s API.
Suppose the original payment has TLID A and the renewal receives TLID B. The renewal’s own identifier is B; its original reference remains A.
Store those roles separately. Automatically replacing the original reference with every new response can destroy that distinction.
Which TLID dates should merchants track
For Mastercard’s Transaction Link ID 1240 clearing edit, the comply-by date is August 1, 2027. Assessments begin September 26, 2027.
Mastercard’s October 27, 2026 bulletin gives the following schedule.1
| Milestone for the Transaction Link ID 1240 edit | Date |
|---|---|
| Monitoring began | June 2, 2026 |
| Notifications began | July 1, 2026 |
| Extended comply-by date | August 1, 2027 |
| Assessments begin | September 26, 2027 |
The edit covers First Presentment/1240 messages: financial records submitted for clearing in Mastercard’s dual message system. Authorization and clearing use separate message stages.
This extension applies to that clearing edit. Confirm the current requirement for each of your payment flows with your provider.
Provider guidance currently differs. Checkout.com’s November update lists August 1, 2027 for economically related transactions. Adyen’s guidance lists October 23, 2026 for its MIT requirement.
Ask for the applicable bulletin, message type, implementation date, and assessment date in writing.
How TLID relates to the references you already store
Your payment integration may already have a provider payment ID and a network transaction reference. Adding TLID creates another mapping to manage.
| Reference | What to check |
|---|---|
| Provider payment ID | Which payment record it identifies inside that provider |
| Existing network reference or Trace ID | Whether the provider still requires it alongside TLID |
| Payment’s own TLID | Which transaction received that identifier |
| Original TLID reference | Which earlier transaction the later payment links to |
Adyen requires both its Trace ID and TLID fields. Checkout.com also describes handling both identifiers. Retain existing references until your provider confirms they can be removed.
Who needs to change their integration
The answer depends on who stores the credential and who processes the next payment.
Adyen says it handles TLID storage and transmission for merchants using Adyen Tokenization. Its external-tokenization guidance assigns integration work to the merchant.
Checkout.com can resolve the TLID when it processes the original CIT and later MIT using the appropriate payment reference. Its cross-provider guidance requires the merchant to capture, store, and send the TLID.
Same provider
External vault or another provider
Confirm responsibilities for your API version, vault arrangement, and processing route.
Why TLID matters when you use multiple providers
Imagine a customer starts a subscription through provider A. Six months later, your team sends the renewal through provider B.
The billing platform has the stored credential and active agreement. Provider B still needs the original reference in the field its integration expects.
Suggested verification path. Confirm supported reference handling with both providers.
Trace the field through your vault, which stores payment credentials or their references. Include your billing platform and orchestration layer, if you use one to manage routing.
Check every connector along that route. A field can exist in your database and still be omitted from the receiving provider’s request.
What merchants should do now
1 Map the fields on every route
Record the response field, storage location, outbound request field, and owner for each provider.
| Provider | TLID fields to map | Existing reference to retain |
|---|---|---|
| Adyen | additionalData.transactionLinkId | additionalData.networkTxReference |
| Checkout.com | processing.scheme_transaction_link_id | The applicable previous_payment_id reference |
| J.P. Morgan | Response transactionLinkId; request originalTransactionLinkId | Applicable network transaction identifiers |
Confirm full field paths and requirements for your API version.
2 Check storage with actual responses
Inspect eligible payment responses. Check that parsing, storage, export, and retrieval preserve all 22 characters.
Keep the original reference with the relevant credential setup and payment agreement. Store each payment’s own TLID in its transaction record.
3 Plan for older subscriptions
Separate records with an original TLID from records without one. Group missing records by provider and available payment history.
Checkout.com documents a historical fallback using a successful, non-disputed recurring payment within the last three months. Confirm eligibility with the receiving provider before applying that approach across routes.
4 Test a payment across providers
Follow the original reference from provider A’s response to provider B’s request. Check its meaning at the destination.
An approval alone does not show which reference reached Mastercard. Request transmission evidence from the processor.
5 Check clearing as well as authorization
For transactions covered by the Mastercard clearing edit, the TLID must be present and match the authorization response, subject to applicable exclusions.1
Yes
No
Simplified view of the missing-or-mismatched test in GLB 11418.5. The acquirer applies the complete edit criteria.
Ask your acquirer, the institution acquiring your card transactions, for results under edit 27, Transaction Link ID 1240.
Request missing and mismatched counts, transaction samples, affected routes, and applicable exclusions. The bulletin lists a 20,000-transaction baseline and a 98% threshold for this acquirer edit.1
Acquirer implementation guidance
Use the guidance for your provider and API version when planning the integration:
- Adyen TLID guidance explains tokenization responsibilities, the TLID field, and the existing Trace ID field.
- J.P. Morgan Payments TLID guidance distinguishes a payment’s own TLID from its original transaction reference, with examples by transaction type.
- Worldpay Access Payments TLID guidance covers recurring-payment linking, lifecycle handling, and migration of existing references.
Worldpay’s page is marked preview, with estimated availability in Q4 2026. Confirm availability for your integration before implementing its examples.
Common TLID questions
Can we generate a missing TLID ourselves
Receive the Mastercard-generated value through your provider. Ask the provider how to handle historical records when that value is unavailable.
Should we overwrite the original TLID after every renewal
Keep the payment’s own identifier and the original reference separate. Follow the provider’s rules for historical fallbacks and new credential setups.
If our provider handles TLID automatically are we finished
Verify the arrangement for your actual payment routes. Include external vaults, backup providers, migrations, and clearing.
Start with one subscription
Choose one active subscription. Trace its original reference from the source payment through storage to the next renewal.
Then add three weekly exception checks: new setups missing an original reference, renewals missing the required reference, and clearing mismatches reported by acquirers.
Assign an owner to each exception. Separate older records from new failures so a historical backlog does not hide a broken integration.
For related context, read the Atlas NTID field guide.
Sources
1. Mastercard, GLB 11418.5 Data Integrity Monitoring Program Edit for Transaction Link Identifier, October 27, 2026, pages 1–4.
- Mastercard Send Release Notes 26.1, page 8. The API rollout described is specific to Mastercard Send.
- Checkout.com TLID guidance, updated November 11, 2026.
- Worldpay Access Payments TLID guidance, updated November 10, 2026; preview functionality.