Known Issues

Our REST API specification shows that the field

merchantInformation.merchantDescriptor.alternateName

has a maximum character value of ≤ 13 characters. However, the validation is not working and allows more than 13 characters.

Developers using the REST API.

None.

None.

Optional text messages from issuers to cardholders in multibyte characters might not be displayed properly in Frictionless Payer Authentication Enrollment transaction responses for merchants. As a result, merchants might not be able to display the multibyte characters to cardholders on merchant sites in readable format.

Merchants who use Frictionless Payer Authentication Enrollment and cardholders with text information provided by the ACS/Issuer, which can include possible follow-up actions to be done for their authentication transactions.

None.

None.

An intermittent issue sometimes prevents Mastercard Token Requestor Identifier (TRID) enrollment from returning the TRID value in the Business Center, despite showing a success message.

Merchants who process network token transactions.

None.

None.

Microform transient tokens created using the version 2 JavaScript libraries are prevented from being authorized.

Merchants who use Microform version 2.

The error is generic due to a mapping issue.

None.

An intermittent issue in our testing environment sometimes causes the Decision Manager Detail Report to have two columns that have the same data, but with two different names. The names are

Device Fingerprint Date Device First Seen

and

Device Fingerprint Device First Encounter

.

Users of the Decision Manager Detail Report.

None.

None. The report works correctly in the production environment.

When a user performs a case search based on a particular Decision Manager profile, only a subset of the result is returned. However, a general case search based on a time period returns the full results. A free-text case management search also does not return the correct results.

Users of Decision Manager Case Results.

None.

Use a general case search and filtering it according to your needs.

Sometimes when a user deletes a token, it still appears active in the Business Center.

Users of the Token Management Service.

None.

None.

When a Payer Authentication Validation request is sent to perform a non-payer authentication transaction using a JCB payment card, the response might be a

DINVALIDDATA (102)

error regarding a CAVV cyptogram.

Merchants using Payer Authentication to perform non-payment authentication calls using JCB cards.

The Payer Authentication Validation service currently expects a CAVV cryptogram in the response payload. However, we have been informed that JCB does not return a CAVV for non-payment authentication.

None.

Case Management searches for payment transactions that span mutliple dates and use merchant-defined data return incomplete results. This does not apply to non-payment requests (Decision Manager only).

Users that use merchant-defined data to search within Case Management.

None.

None.

When creating, copying, or editing a recurring report subscription, if you set the start time to 12XX PM (where XX is any value between 00 and 59), the action fails with a red banner error that says

Failed to create report

.

Also, when creating, copying, or editing a recurring report subscription, if you set the start time to 12XX AM (except 1200 AM), the subscription gets saved with start time 12XX PM instead.

These issues affect all time zones.

Merchants who use recurring report subscriptions.

None.

The only variation of 12XX AM or PM that works is 1200 AM.

When Decision Manager rejects a pre-authorization request, the response code is 100 (successful authorization); however, no authorization was sent.

Merchants that use Decision Manager with Payer Authentication.

None.

None.

The SMS (text message) service is currently not working in Canada due to a compliance issue. The issue is triggered when users attempt to receive SMS messages for various functions such as One-Time Password, Decision Manager notifications, and other important alerts. As a result, users will not receive the SMS messages needed for these functions.

None.

None.

Users can use email as an alternative method while the issue with the SMS service is being resolved.

There is an issue that allows merchants whose account is part of a portfolio to use Virtual Terminal even if their account was not given permission to use it by the portfolio administrator.

Merchants whose accounts are part of a portfolio.

None.

If Virtual Terminal is required for the merchant account, it must be enabled on the

Manage Merchants > Product Enablement

page by a portfolio administrator.

A defect is preventing users who use single-sign on (SSO) to log in to the Business Center from deleting a role. The user receives the error message

role cannot be deleted as users exist for the role

even when there is no user assigned to the role.

Users who use SSO to log in to the Business Center.

None.

None.