Known Issues

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.

Cybersource PayPal merchants using the Billing Agreement.

No errors are received by the merchant.

None.

Some customers might receive duplicate messages at their endpoint URL.

Users of RTSS.

None.

None.

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.

Global.

None.

None.

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

Global.

None.

Filter your search by using the

+add filter

option at the top of the page.

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

Users of Decision Manager.

None.

Try the search again. Retries are usually successful.

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.

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

None.

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

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

None.

Contact the support team to configure the

vital_merchant_currency_code

field.

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.

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.

Merchants who use the legacy boarding platform.

None.

Contact the support team.

Merchants who attempt a credit authorization through the SIX platform receieve the error

invalid or missing: cavv

.

Merchants who process credit authorizations through the SIX platform.

None.

None.

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.

Merchants who process invoicing payments through SmartPay.

None.

None.

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

Merchants who use the Token Management System.

The failed retrieval generates the message

Error: An error occurred retrieving the Payment Instrument

.

Use the Token Retrieval API.

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.

Merchants performing transaction search using one of the REST SDKs.

None.

None.

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.

Users of Token Search in the Business Center.

None.

Search using a preset date range.

The webhooks service is sending duplicate notifications for the

invoicing.customer.invoice.paid

event.

Merchants using webhooks for invoicing.

None.

None.