Validate e-wallet card

Validate the data of a card stored in an e-wallet.

EnvironmentMethodEndpoint
Sandboxhttps://apisandbox.cieloecommerce.cielo.com.br/2/zeroauth
Productionhttps://api.cieloecommerce.cielo.com.br/2/zeroauth

The response always indicates whether the card can be authorized at the moment. This information only means that the card is valid for transactions, but does not indicate that a specific amount will be authorized.

The fields returned in the response depend on the validation result. The following table shows all possible fields.

❗️

If the response is negative, do not submit the card for authorization.

Submit the card for authorization only if the Zero Auth verification response code is positive.

Parameters returned in the card validation response for e-wallet:

FieldDescriptionTypeSize
ValidCard Status:
  • True - Valid Card
  • False - Invalid Card
Boolean
ReturnCodeReturn codeText2
ReturnMessageReturn messageText255
Payment.IssuerTransactionIdTransaction identifier generated by the card brand, returned in the Zero Auth response. Zero Auth does not receive this field in the request. Store the value to send it, as mandatory, in subsequent recurring credit and debit transactions. In scheduled recurrence, the field is sent automatically in subsequent transactions. See more details in Card Brand Identifiers.string30
Payment.TransactionLinkIdUnique identifier (TLID) generated by Mastercard and returned in the Zero Auth response. Zero Auth does not receive this field in the request. Store the original value to send it, together with the IssuerTransactionId, in subsequent MIT transactions. See more details in Card Brand Identifiers.
Format: 22 alphanumeric characters (A–Z, a–z), case-sensitive, and may include hyphens (-) and underscores (_).
string22

TLID Mastercard

The Transaction Link Identifier (TLID), sent and returned in the TransactionLinkId field, is a unique identifier generated by the Mastercard card brand during a CIT transaction, used to link the related MIT transactions. The TLID applies to the Zero Auth response (response only) and to credit card, debit card, and merchant recurrence transactions.

For Mastercard, send IssuerTransactionId and TransactionLinkId together in MIT transactions: both parameters are mandatory.

PhaseDateDescription
Phase 1CurrentAvailability of the TransactionLinkId in the responses of card validation by Zero Auth, credit card payment creation, debit card payment creation, and in the query by PaymentId.
Phase 2Starting October 23, 2026Required inclusion of the TransactionLinkId in the request (MIT).

See more details in Card Brand Identifiers.

Body Params
Card
object
string

Conditional obligation Card Token in API E-commerce Cielo. Size: 36.

Wallet
object
Headers
string
required
Defaults to 8937bd5b-9796-494d-9fe5-f76b3e4da633

Store identifier in Cielo. Size: 36. This documentation provides a default MerchantId to allow testing in the sandbox, but you can also provide the enabled MerchantId during the deployment process.

string
required
Defaults to XKGHUBSBKIRXKAVPSKWLVXYCLVJUGTNZLIHPUSYV

Public Key for Double Authentication in Cielo. Size: 40. This documentation provides a default MerchantKey to allow testing in the sandbox, but you can also provide the enabled MerchantKey during the deployment process.

Responses

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json