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

**Paypal** \| EPS-32184
-----------------------

Description
:
When clients pass in the note_to_payer and/or note_to_payee fields for SOAP XML integrations, the values are not transmitted to the processor.

Audience
:
Cybersource PayPal merchants using the Billing Agreement.

Technical Details
:
No errors are received by the merchant.

Workaround
:
None.

**RTSS** \| EPS-32633
---------------------

Description
:
Some customers might receive duplicate messages at their endpoint URL.

Audience
:
Users of RTSS.

Technical Details
:
None.

Workaround
:
None.

**Business Center** \| EPS-32636
--------------------------------

Description
:
Some users of the Business Center with non-administrative roles cannot access the My Profile section. When they attempt to navigate to the My Profile section using the link at the top-right corner of the screen, the page is blank.

Audience
:
Global.

Technical Details
:
None.

Workaround
:
None.

**Transaction Search** \| EPS-32719
-----------------------------------

Description
:
Merchant reference numbers that contain the slash character (/) cannot be searched for using the default search filters.

Audience
:
Global.

Technical Details
:
None.

Workaround
:
Filter your search by using the *+add filter* option at the top of the page.

**Decision Manager** \| EPS-32768
---------------------------------

Description
:
An intermittent issue sometimes causes an error when a user runs a Case Management search.

Audience
:
Users of Decision Manager.

Technical Details
:
None.

Workaround
:
Try the search again. Retries are usually successful.

**Virtual Terminal** \| EPS-32807
---------------------------------

Description
:
Due to an intermittent issue, when a one-time payment is made in the Virtual Terminal, the receipt sent to the customer sometimes shows $0 instead of the transaction amount.

Audience
:
Merchants who use Virtual Terminal to make one-time payments.

Technical Details
:
None.

Workaround
:
Merchants can manually resend the email receipt using the Transaction Summary page, which shows the correct amount.

**Merchant Boarding** \| EPS-31817
----------------------------------

Description
:
When merchants set TSYS as the processor for transacting merchant accounts, they are unable to configure the required field vital_merchant_currency_code in the Business Center.

Audience
:
Portfolio account users who board or configure transacting merchant accounts for merchants who process transactions through TSYS.

Technical Details
:
None.

Workaround
:
Contact the support team to configure the vital_merchant_currency_code field.

**Legacy Mechant Boarding** \| EPS-32091
----------------------------------------

Description
:
An issue is affecting portfolio merchants who use the legacy merchant boarding system. When the Merchant File Upload feature is used to update merchant information, some fields are updated and others are not.
:
**Updated fields:**

    * merchant name
    * country
    * url

:
**Unchanged fields:**
:
* phone
* addressLine1
* city
* state
* postal code

:
There are no plans to fix the legacy platform. Affected merchants are advised to migrate to the Visa Acceptance Platform, where this error does not occur and the platform is regularly updated.

Audience
:
Merchants who use the legacy boarding platform.

Technical Details
:
None.

Workaround
:
Contact the support team.

**Payments** \| EPS-32224
-------------------------

Description
:
Merchants who attempt a credit authorization through the SIX platform receieve the error *invalid or missing: cavv*.

Audience
:
Merchants who process credit authorizations through the SIX platform.

Technical Details
:
None.

Workaround
:
None.

**Invoicing** \| EPS-32398
--------------------------

Description
:
When merchants process invoicing payments through Smartpay and their customer's invoice payment is declined with error *RC 401*, the invoice's status is set to Pending and cannot be canceled.

Audience
:
Merchants who process invoicing payments through SmartPay.

Technical Details
:
None.

Workaround
:
None.

**Token Management System** \| EPS-32701
----------------------------------------

Description
:
Merchants are unable to retrieve a Payment Instrument token in the Business Center.

Audience
:
Merchants who use the Token Management System.

Technical Details
:
The failed retrieval generates the message *Error: An error occurred retrieving the Payment Instrument*.

Workaround
:
Use the Token Retrieval API.

**REST SDKs** \| EPS-32170
--------------------------

Description
:
In the REST SDK's transaction search, the field embedded.transactionSummaries.processorInformation.eventStatus is missing from the response payload. Merchants require this field to validate the status of their capture and refund transactions.

Audience
:
Merchants performing transaction search using one of the REST SDKs.

Technical Details
:
None.

Workaround
:
None.

**Token Management Service** \| EPS-32297
-----------------------------------------

Description
:
When you search for a token in the Business Center using a custom date range, the first page of results loads normally. However, clicking any other page causes a yellow warning banner to appear, and the search results are reset to 0.

Audience
:
Users of Token Search in the Business Center.

Technical Details
:
None.

Workaround
:
Search using a preset date range.

**Webooks** \| EPS-32439
------------------------

Description
:
The webhooks service is sending duplicate notifications for the `invoicing.customer.invoice.paid` event.

Audience
:
Merchants using webhooks for invoicing.

Technical Details
:
None.

Workaround
:
None.