Known Issues

The validation performed against the email address entered in the Recurring Billing portal in the Business Center differs from the Virtual Terminal and our APIs. Email addresses with the format

<string>@<string>.<string>-<string>.com

will not be allowed in the Recurring Billing form.

Recurring Billing users.

None.

None.

A defect was discovered that happens when a Payer Authentication Enroll request is sent by a merchant whose account configuration contains an incorrect country code value. The resulting error code is a generic

ESYSTEM

code instead of a more meaningful code that indicates the problem.

Users of Payer Authentication.

None.

Call Customer Support to have your configuration updated to include the correct merchant country code.

A defect was discovered that causes custom reports in the Business Center to fail when the time zone is set to

Asia/Rangoon

.

Merchants who create custom reports in the Business Center.

None.

Choose a different time zone.

A defect was discovered that affects merchants who are payment aggregators and use Amex Direct as their payment processor. When these merchants submit the Merchant Category Code (MCC) through the API, the code does not take precedent over the code that is already stored in their merchant configuration, which could lead to transaction failures.

Merchants processing aggregator transactions on Amex Direct and send the MCC in API requests.

None.

None.

Users who submit Electronic Check Debit requests through Payer Authentication may encounter an error message stating

The following request fields is either invalid or missing: IPAddress

. This issue arises when an IPV6 address, which is a 39-character string, is passed into the

deviceInformation

field using the REST API.

Users of Payer Authentication and Electronic Check Debit.

The Cardinal gateway is designed to accept an IP address with a maximum length of 20 characters.

Use an IPV4 address.

Clicking the Pay button multiple times when using PayByLink can result in multiple charges.

Users of PayByLink.

None.

None.

The REST API field

merchantInformation.merchantDescriptor.alternateName

is inconsistently validated for some payment services by our servers. This can lead to incorrect information being accepted as successful.

Users of the REST API.

None.

The reconciliation ID is not being returned in credit transaction responses.

All Simple Order API and SOAP Toolkit API users who perform credit transactions and want to capture the reconciliation ID.

The

ccCreditReply_reconciliationReferenceNumber

field was not mapped correctly.

None.

There is an intermittent issue that sometimes causes the Credit option to become unavailable for transactions in the Transaction Details page of the Business Center.

Users of the Business Center.

None.

Use a stand-alone credit instead of a linked credit.

Merchants using the Edge browser who use the Business Center’s Merchant Switch feature to switch to a subordinate merchant account and then attempt to create a new subscription in Recurring Billing might receive an error message saying

Try Again Later

.

Users of Edge, Merchant Switch, and Recurring Billing.

None.

Using Google Chrome does not trigger this error.

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.