Known Issues

A defect is causing follow-on transactions that are more than 60 days after the original transaction to fail. A follow-on transaction is one that references the transaction ID of the original transaction, typically a refund.

Merchants that send follow-on transactions.

The error message for these failed transactions is

The field is invalid: paymentInstrument.card.expirationYear

.

Use a stand-alone credit instead.

When a customer or merchant sending an API payment transaction incorrectly sets the

card_type

field to a value of

JCB

when the card is Visa or Mastercard, our system identifies the correct card type and sends the transaction correctly to its destination. However, the transaction is incorrectly stored in our system as a JCB card. This defect creates these issues:

The batching and settlement of the transaction treats it as a JCB transaction, causing clearing issues at the acquirer’s end.
Reporting and transaction search results display the transaction as JCB.

Merchants who use our API on Visa Platform Connect.

None.

If you are using the

card_type

field in your API transaction payload, consider adding a validation on your end to catch and correct incorrect customer input.

Credit authorization transactions processed through the SmartPay processor using the Japanese Yen (JPY), with a transaction amount less than 6,500 JPY, are erroneously processed.

Merchants who send credit authorization transactions through SmartPay using the JPY currency.

None.

None.

When a merchant who uses Cielo as a processor sends an authorization transaction during a time when Cielo has high traffic, our system processes it as a timeout and returns an ESYSTEM error to the merchant's system. However, if the transaction later goes through on the Cielo end, they send back a success message that our system ignores because in our system, the transaction is logged as a timeout. If the merchant sends a second message before the Cielo response and it succeeds, the customer might see two pending authorizations in their bank account. However, one of the authorizations will not go through, and the customer will be charged only once.

Merchants that use Cielo as a processor.

None.

None.

The validation performed against the email address entered in the Recurring Billing portal in the Business Center differs from the Virtual Terminal and our APIs. Email addresses with the format <string>@<string>.<string>-<string>.com will not be allowed in the Recurring Billing form.

Recurring Billing users.

None.

None.