VerifyCard by card number

This is your first endpoint! Edit this page to start documenting your API.

EnvironmentMethodEndpoint
Sandboxhttps://apisandbox.braspag.com.br/v2/verifycard
Productionhttps://api.braspag.com.br/v2/verifycard

In the request to VerifyCard, you will send the Provider along with the card data (number or card token).

In the response, the Zero Auth verification will be displayed in the Status, ProviderReturnCode, and ProviderReturnMessage properties. The return of the BIN Query (card characteristics) will be in the properties of the BinData node.

Card brands available per acquirer in Zero Auth:

  • Cielo: Visa, Master and Elo
  • Getnet: Visa, Master, Elo and Amex
  • Rede: Visa, Master and Elo.
⚠️

Zero Auth Status

The result of the card validation will be displayed in the Status field; check the possible values:
“0” - Zero Auth query failed
“1” - Zero Auth query successful
“99” - Query successful, but the card status is inconclusive

ℹ️

For the Rede2 provider, the response will return the BrandTransactionId, which is the identifier of recurring transactions with the flags at the Rede acquirer.

📘

Important

If the API returns error 389 – Registration Restriction, contact the commercial manager to check if the service is correctly enabled; if it is, the response indicates that this attempt cannot be validated due to Cielo's internal criteria. We recommend trying another card to complete the validation.

ℹ️

Tokenized Visa Card Verification Transactions

Starting on 04/17/2026, it will be required to send the cryptogram in card verification transactions using tokenization with the Visa card brand:

  • Send the DPAN (token) in the Card.CardNumber field;
  • Send the cryptogram in the Card.SecurityCode field.

Exclusive for the Cielo acquirer.

TLID Mastercard

The Transaction Link Identifier (TLID) is a unique identifier generated by the Mastercard card brand during a transaction. It is created in the initial transaction (CIT) and must be used to associate all subsequent transactions (MIT) within the same cycle.

PhaseDescription
Phase 1Availability of the TransactionLinkId in the responses of VerifyCard by card number, credit card payment creation, debit card payment creation, and in the query by PaymentId.
Phase 2Required inclusion of the TransactionLinkId in the request (MIT) starting Oct 23, 2026

See more details in Brand identifiers for Cielo.



Body Params
string
required

Name of the payment provider. For sandbox, use the value 'Simulado'. Size: 15.

Card
object
Headers
string
required
Defaults to e3c24810-18bb-4bd7-88a0-a36d6b4a0731

Merchant identifier in Gateway de Pagamento. Size: 36.
This documentation provides a default MerchantId for sandbox testing, but you can also use your enabled MerchantId during deployment.

string
required
Defaults to GQUAIWVDKUINZRHDQPLHUVHAIIFEIXFEXWPOYGHY

Public key for dual authentication in the Gateway de Pagamento. Size: 40.
This documentation provides a default MerchantKey for sandbox testing, but you can also use your enabled MerchantKey during deployment.

string

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Response

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