Known Issues {#rn-known-issues}
===============================

**Virtual Terminal** \| EPS-37322
---------------------------------

Description
:
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.

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

Technical Details
:
None.

Workaround
:
None.

**Fraud Management Essentials** \| EPS-37175
--------------------------------------------

Description
:
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*.

Audience
:
Users of Fraud Management Essentials.

Technical Details
:
None.

Workaround
:
None.

**Credit Authorizations** \| EPS-37776
--------------------------------------

Description
:
When a Credit Authorization is submitted using the REST APIs */credit* endpoint and the authorization fails, the submitTimeUtc field is not returned.

Audience
:
Users of the REST API.

Technical Details
:
None.

Workaround
:
None.

**Voids** \| EPS-37884
----------------------

Description
:
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.

Audience
:
Merchants in India.

Technical Details
:
None.

Workaround
:
None.

**Payments through TSYS** \| EPS-37988
--------------------------------------

Description
:
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).

Audience
:
Merchants who process transactions through TSYS Acquiring Solutions.

Technical Details
:
None.

Workaround
:
None.

**Partner Risk Controls (PaRC)** \| EPS-38258
---------------------------------------------

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

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

Technical Details
:
None.

Workaround
:
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.