Brand identifiers for Cielo acquirer
Some card brands return identifiers in the authorization response or in the card validation response (VerifyCard). These identifiers link related transactions throughout the payment cycle, improving approval rates in recurring payment and stored credentials (Card on File) scenarios.
Always store the identifiers returned by the API for use in subsequent transactions.
| Identifier | API field | Card brands |
|---|---|---|
| Issuer identifier | IssuerTransactionId | Visa, Mastercard, Elo, American Express |
| Transaction link identifier | TransactionLinkId (TLID) | Mastercard |
IssuerTransactionId
The IssuerTransactionId is an identifier generated by the issuer to associate an original transaction with future operations from the same cardholder. It improves the approval rate because the issuer recognizes the link to a previous cardholder-initiated transaction (CIT).
Warning: the
IssuerTransactionIdvalue may change with each new authorization or card validation. Always store the identifier returned in the most recent transaction and send it in subsequent transactions.
Card brands: Visa, Mastercard, Elo, and American Express.
Available in responses from: credit and debit authorization, recurring payments, Zero Auth, and query by PaymentId.
Response example:
{
"Payment": {
"Type": "CreditCard",
"IssuerTransactionId": "580027442382078"
}
}TransactionLinkId (TLID)
The TransactionLinkId (TLID) is a Mastercard identifier for linking related transactions within the same transactional cycle. Sending the TLID is independent of the IssuerTransactionId — both may be required in the same transaction.
Card brand: Mastercard.
Available in responses from: credit and debit authorization, recurring payments, Zero Auth, and query by PaymentId.
Response example:
{
"Payment": {
"TransactionLinkId": "mK8vT2qA-9LpX7dWc3Rf_HsD1Z"
}
}TLID implementation phases
The TLID rollout occurs in two phases:
Phase 1 — TLID availability (coming soon)
The TransactionLinkId will be returned in API responses for Mastercard transactions. Required action: start storing the TLID for future use.
Phase 2 — Mandatory TLID submission (Oct 23, 2026)
Sending the TransactionLinkId becomes mandatory in merchant-initiated transactions (MIT), referencing the previous transaction (CIT or prior MIT).
The request parameters for sending the TLID in MIT requests will be available in the Cielo APIs before October 2026.
Use in CIT and MIT scenarios
In stored credentials and recurring payment scenarios:
- CIT (Cardholder-Initiated Transaction): transaction initiated by the cardholder — generates the identifier.
- MIT (Merchant-Initiated Transaction): transaction initiated by the merchant — must reference the identifier from the original CIT or the previous MIT.
For more information, see Transaction initiator indicator (CIT and MIT).
See also
- Card on File
- Transaction initiator indicator (CIT and MIT)
- Create a credit card payment
- VerifyCard by card number
- Get payment details via PaymentId
Updated 18 days ago