Changelog

• See how to access them in How to generate the SOP credential?.

• 6 – Operation Successful, or
• 9 – Time Out

• Updated from up to 15 characters to up to 11 characters.

• It is not necessary to send the cryptogram in tokenized MIT transactions for the Mastercard card brand, because the token was already validated in the original CIT transaction.
• Learn more at Transaction Initiator Indicator (CIT and MIT)

New page about providers and brands supported by the API Gateway de Pagamento added;

Guidance on using 3DS authentication for credit card and debit card added:

• The validation and return of the Payment.Eci field occur only in the production environment at this initial stage;

Guidance on using multi-benefit card payments added:

• Please refer to the standard voucher integration when using multibenefícios Alelo;

Guidance for Alelo voucher cancellation added:

• Partial cancellation is not possible;
• Full cancellation can only be performed on the transaction day (D0);
• To cancel after the transaction day (from D+1 onwards), you must contact Alelo;

Guidance for batch capture and cancellation via the e-commerce portal added:

• The API allows you to capture or void transactions individually. To capture or void a group of transactions, use the e-commerce portal;

Guidance for canceling debit transaction via PaymentId added:

• For debit cards, only one partial void is allowed;

Guidance on error 389 – Registration Restriction for Zero Auth added:

• If the API returns error 389, 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;

• When the card is tokenized, Click to Pay returns the CAVV and sending the security code is not required.
• When the card is not tokenized, sending the security code is required.

• An explanatory diagram of the process was included, covering the previous step and the authorization call.

• Indicates a failure in validating the credentials sent.

• To confirm if authentication was applied during authorization, check the ECI value in Payment.Eci;
• The API replicates the ECI provided by the merchant in Payment.ExternalAuthentication, but the actual value used by the card brand is the one in Payment.Eci.

• If the provided MerchantId does not exist in the environment database (Production or Sandbox), the error "298 – Split payment facilitator data not found" will be returned.