• New CardNumberType field allows sending transactions with or without a cryptogram in payments with a network token via external integration;
• Hipercard and Amex added to the card brands supported by the IssuerTransactionId in a recurrence;
• New required fields for payment facilitators;
• Polling time reduced from 30 to just five minutes;
• Possibility to configure trusted IPs on the Cielo website;
• New error code (340) added to the cancellation return codes table;
• New fields Wallet.ReceiverData.Name and Wallet.ReceiverData.CompanyName for SDWO transactions.

Starting from April 11, 2025, Visa will return two new codes for declined transactions in category 2, where the issuer cannot approve at the moment. The codes are:

• 5C (transaction not supported/blocked by the issuer): will be returned by Visa for all declines due to issuer rules for a specific card range or BIN;
• 9G (blocked by the cardholder - contact the cardholder): will be returned by Visa when the cardholder specifies a transaction block through transaction and card control tools (such as an app).

ℹ️

Check the complete rules for retrying category 2 codes in the Visa Retry Program.

• Improvements in the 3DS authentication content;
• Improvements in the Data Only content;
• Correction of the example for the concatenation of ClientId and ClientSecret for 3DS authentication;
• Warning about new required fields for Payment Facilitators.

Starting May, 25, 2025, Visa will implement changes in their retry program, in order to improve authorization processing and user experience.

The number of retries allowed after refused transactions within codes in categories 2, 3, and 4 will increase for 20 attempts in 30 days.

Please refer to Card brands retry program for more information.

• Visa Data Only authentication for Caixa is unavailable.
• Added information that the Payment.Capture parameter determines only the behavior of the first transaction on a create recurring payment;
• New page instructing how to view MerchantId and MerchantKey credentials on the Cielo website;
• New page instructing how to revoke and create credentials on the Cielo website;
• Details added about Cybersource and ClearSale ;
• Recomendation on sending the Payment.CreditCard.Cryptogram parameter in payments with nteworke token via external integration.

• Update of card numbers for test purposes;
• Addition of information about default URL for <a href="https://docs.cielo.com.br/ecommerce-cielo-en/docs/notification-post target="_blank">notification Post;
• Updated information about sending card needing to start with 5 and be valid in mod10 in simulate validation in Zero Auth;
• Addition of list of MCCs allowed for CBPS;
• Update of MCC in cash In transactions;
• Addition of description for error code 308 in API errors;
• New note on capture;
• Update of description for codes 10 and 11 in transactional status;
• New page on pix account management at Cielo.

• New response examples for transaction queries by PaymentId for transactions with different payment methods;
• Added information saying that, for sandbox transactions with 3DS authentication, the bpmpi_merchant_url field must be sent as "https://localhost" when mapping the classes;
• New page detailing how to generate credentials for Silent Order Post;
• New recurrence status list page;
• New payment method Click to Pay available for integration.

• Created new page detailing Soft Descriptor;
• Added a warning informing the TLS certificate version;
• Created new page instructing how to get the 3DS credentials;
• Created new Antifraude status list page;
• Elo network now available for boarding tax by airlines;
• Added a warning about the possibility of performing more than one partial void for credit and debit transactions;
• Added notice to join the Google Pay user group to facilitate integration.

• New note about capturing amounts lower than 20 cents;
• Foreign card brands updated to inform that they do not accept installments;
• Maximum period for capture updated from 15 to 7 days;
• Updated description for API error 301.