Debit card

ℹ️

Please refer to the API Reference for the full request and response examples.

This payment method is automatically configured along to Cielo’s affiliation.

Every debit transaction should be authenticated by demand of the issuing banks and card brands, to ensure better safety.

To authenticate a debit transaction, we use the EMV 3DS 2.2 protocol; this protocol is a script integrated to your e-commerce that verifies the identity of the shopper while keeping a positive shopping experience and reducing the risk of fraud.

To integrate the 3DS authentication method, please refer to 3DS Authentication.

⚠️

WARNING

Cielo doesn't offer the first version of the authentication protocol (3DS 1.0), since card brands and issuers are discontinuing this option.

ℹ️

Debit without authentication

Or “debit without password”, can only be done when the e-commerce is authorized by the issuing bank to dismiss the authentication. In case you have that permission, send the field Authenticate as "false" in the standard request for debit card.

⚠️

Validating a card

A transaction with its value (Amount) as 0 is not allowed. To verify if a card is valid, use Zero Auth.

Authenticating a debit transaction

In the standard debit transaction (with authentication), send Authenticate = "true". Please refer to 3DS Authentication for more information.

Mastercard credit card transactions with stored credentials

Mastercard brand requires the Transaction Initiator Indicator for credit and debit card transactions using stored card data.

The goal is to indicate if the transaction was initiated by the cardholder or by the merchant. In this scenario, the node InitiatedTransactionIndicator must be sent with the parameters Category and SubCategory for Mastercard transactions, within the Payment node.

Please check the complete list of categories in the Category parameter description and the subcategories tables in Transaction Indicator Tables.