Known Issues

There is a flaw in processing some Mastercard transactions when using Chase Paymentech as a processor. If a Mastercard payment transaction uses a network token containing card credentials and received a successful Payer Authentication response, the transaction fails when it is received by Chase Paymentech.

Merchants who process Mastercard transactions through Chase Paymentech and use Payer Authentication and network tokens.

The transaction request fails because unnecessary data is added to it by our system.

Do not migrate Mastercard tokens to network token until the defect is resolved.

An intermittent issue sometimes causes the Transaction Details page to wrongly identify the Token Type of a transaction and generate a hyperlink which fails to return results.

TMS users relying on Transaction Details pages.

None.

Navigate to the Token Management > Customers page and filter the results using the token displayed in the Transaction Details page.

Attempts to use our testing environment to test FDI Global API processor test triggers for Partial Authorization are not returning an expected value in the field

auth_account_balance

if the merchant category code (MCC) is not set correctly.

Merchants for FDI Global who test Partial Authorization API transactions in our testing environment.

Configure merchants in the testing environment with a valid MCC when using FDI Global as a processor.

Some portfolio merchants are unable to assign Meta Keys to subordinate accounts.

Users of merchant boarding and meta keys.

None.

None.

API requests that combine Payer Authentication with authorization and include relaxed AVS return a billing information error.

Users who send API requests combining Payer Authentication and Authorization with relaxed AVS.

None.

Send separate Payer Authentication and Authorization requests.

There is an intermittent issue that sometimes causes an HTTP 500 timeout response when you are using the REST API to download the Batch Upload report with a large number of transactions.

Merchants who download the Batch Upload report using the REST API.

None.

Download the report in the Business Center.

A merchant that deleted their service account was affected by an issue that caused end users who attempt to pay an invoice to be shown the error message

Failed to retrieve invoice details

.

Users of invoicing.

Deleting the service account triggered the defect.

Create a new merchant account until the defect is fixed.

When a merchant deletes the Secure Acceptance profile associated with their merchant accounts in the Business Center, the associated merchant accounts become unable to process invoice payments.

Users of invoicing.

None.

Create new merchant accounts until the defect is fixed.

Portfolio accounts in India that use the legacy merchant boarding platform and use Payer Authentication are still required to enter the

-1000

suffix in the acquirer ID field in the Payer Authentication Configuration page. If the suffix is not included, the following error message is shown:

Invalid Acquirer ID

. Users not in India and users of the new platform do not need to add the suffix.

Portfolios in India that use the legacy merchant boarding platform.

None.

Add the suffix.

When a user changes a merchant’s time zone in the Business Center's Merchant Details page by editing the Merchant Information section, the time zone appears to change but the time zone is not changed.

Users of Merchant Management.

None.

Call customer support and request that the time zone be updated.

When a merchant chooses the Settle option in the Orders Pending Review tab, the Accept Case Results dialog displays the message

No follow-on transaction requested

, and the settlement does not occur.

Users of Fraud Management Essentials in the Business Center.

None.

Settle the transaction using the Settle option in the Order Search page.

MIT/COF transactions that use Discover or Diners card are returning a Network Trace ID containing letters. Subsequent transactions then fail due to a front-end validation.

Merchants processing Diners or Discover MIT/COF transactions on Visa Platform Connect.

A 102 DINVALIDDATA error is returned that says:

Field contains non numeric values: subsequent_auth_transaction_id

.

Manually stripping the initial four letters and the space bypass our validation. However, some issuers reject this workaround.

A small number of merchants are experiencing an intermittent issue that causes the Extended Settings page of Decision Manager to display without settings or display with settings that cannot be edited.

A small number of merchants who use Decision Manager.

None.

None.