Known Issues

In the Virtual Terminal, when the ZIP/Postal Code is set as Required, that requirement is not being enforced for countries other than the U.S. and Canada.

Merchants outside the U.S. and Canada who use the Virtual Terminal.

None.

None.

Exporting the Rule Performance Report generates incorrect values, causing numeric fields to appear duplicated. For example, a field that contains

123

is exported as

123123

.

Users of Fraud Management Essentials.

None.

None.

When a Credit Authorization is submitted using the REST APIs

/credit

endpoint and the authorization fails, the

submitTimeUtc

field is not returned.

Users of the REST API.

None.

None.

When a merchant in India attempts to void a transaction in the Business Center, an error message appears that says:

Request failed due to system error

, even in cases where the void was successful.

Merchants in India.

None.

None.

A bug is triggered when a merchant submits a request for a combined authorization and capture transaction that includes the

ignore_bad_cv

field with a value of

yes

. If the authorization part of the transaction is hard-declined (Reason Code 203), the transaction is captured. This is incorrect because the transaction should be captured only for a soft-decline (Reason Code 230).

Merchants who process transactions through TSYS Acquiring Solutions.

None.

None.

PaRC users are unable to remove MIDs (merchant accounts) from PaRC profiles.

Merchants in Central Europe, the Middle East, and Africa.

None.

Create a temporary profile, set the temporary profile to default, and then delete the temporary profile. This removes the default tag from the current profile, which fixes the problem.