• Guidance on using Click to Pay added:
  • 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.
• The usage flow for 3DS with Silent Order POST added to the documentation:
  • An explanatory diagram of the process was included, covering the previous step and the authorization call.
• Added codes 100, BP900 and BP903 to the void return codes table:
  • 100: Transaction not found for void. This occurs when a partial void attempt is made before settlement.
  • BP900: Operation failed. Try again in 5 minutes. We recommend running a transaction status query before making a new request.
  • BP903: Void failed. Try again.

• Guidance on authentication verification in 3DS in credit and debit transactions:
  • 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.
• Information about the SentOrderId field in credit and debit transactions:
  • When MerchantOrderId does not comply with the acquirer’s rules, a new order number is generated and returned in SentOrderId.
  • If the format is valid, SentOrderId returns the same value provided in MerchantOrderId.
• Rule for the Visa Retry Program:
  • Code 14 is now considered in Category 1 and also in Category 3 (Data Quality).
• Error code 100 in void operations:
  • Occurs when a partial void attempt is made before the transaction is settled.

• Inclusion of error code 003 – Nonexistent transaction in ABECS return codes.
• New status lists for Pix, boleto, e-wallets, debit, and credit transactions.
• New scheduled recurrence amount update feature, allowing the client to schedule future adjustments to the subscription amount for a specific date.
• New enable and disable e-wallet functionality on the Cielo website, available for Apple Pay, Google Pay, and Samsung Pay.
• Information about Alelo voucher enablement: the request must be sent directly to Alelo.

• New content about the types of tokenization offered by Cielo.
• New content about payment facilitators;
• Debit card available for payments by e-wallets;
• Information about the minimum installment amount (R$ 5.00);
• Information about retroactive charges when scheduling recurring payments for a past date;
• The ServiceTaxAmount field is now accepted for travel agencies, in addition to airlines;
• Automatic Billing Update (ABU) is now supported for Visa and Elo brands, in addition to Mastercard.

• Instructions for integrating scripts for 3DS and Silent Order Post;
• Information that MCC 6540 is required for SDWO transactions with identified and unidentified boleto under the Mastercard brand;
• Added Alelo brand for payments with voucher;
• Included error code 228 in the possible API errors;
• New instructions on revoking 3DS credentials on the Cielo website;
• New instructions on revoking SOP credentials on the Cielo website;
• New payment method available: multibenefit voucher. Available for Visa, Mastercard and Elo;
• Inclusion of MAC CODE 43 in the Mastercard retry response table;
• Requirement to identify transactions originating from payment links for Elo-branded cards starting from 09/15/2025.

• More information about the MAC 02 code added;
• Example response for getting payment details by TId updated;
• New required field PaymentFacilitator.SubEstablishment.EstablishmentUrl for payment facilitator transactions;
• The Customer.Name field does not accept numbers and special characters;
• New ChangeType code = 25 for Notification Post. The new code indicates that the transaction was either canceled or partially refunded;
• Voucher Alelo is now available as a payment method;
• Instructions for sending the bpmpi_billto_state and bpmpi_shipTo_state fields in the script for 3DS authentication updated for different countries;
• Code 14 from the Visa Retry Program moved from category 1 to category 3 following the brand's directive;
• New test cards available for 3DS Data Only.

• New page about obtaining the cancellation letter via the Cielo website;
• New page detailing how to cancel a sale via the Cielo website.

• Added a note about codes 12 and 15 being converted by the Visa brand;
• Added a note about payment with two cards in the Cielo E-commerce API;
• Updated query time via Cielo website;
• New page for Automatic Billing Updater (ABU);
• Added information about fields returned if the store has ABU enabled;
• Updated information about environments for 3DS authentication;
• Added a note about status 12 returned in the response of a request with currency conversion;
• Added information about Pix temporary account at Cielo in Pix refund rules, Pix account management at Cielo, and Request a Pix refund;
• Updated information about the number of retry attempts allowed for Visa;
• Added new instructions about mandatory recaptcha and token validation for access to the Cielo website;
• New page for How to start using the Cielo E-commerce API;
• Added the fields Wallet.ReceiverData.Name and Wallet.ReceiverData.Identity in SDWO.

• 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.