Known Issues

Merchants who attempt to create a report in the Business Center using the time zone “Asia/Rangoon - (GMT +06:30) Myanmar Standard Time” receive the error message “Error: Failed to create the Report” and the report is not created.

Users who create reports in the Business Center.

None.

None.

Transactions that included a company name with a single apostrophe were being approved for authorization and capture but not for follow-on credits.

Merchants whose company name includes a single apostrophe.

None.

None.

A possible defect caused a few transactions not to appear in the Payment Batch Detail Report (PBDR). The transactions were restored after reports were regenerated. We are investigating.

Only one merchant is known to have experienced this problem but it could affect others.

None.

Regenerate the PBDR or create a one-time report.

If the

jcn_gateway_credit

field is null, it defaults to

true

and initiates a credit authorization. However, credit authorization should only be initiated when the

jcn_gateway_credit

option is enabled.

Merchants that use the JCN gateway.

None.

None.

When a customer enters an incorrect PIN on a payment device that uses the REST API, the value of the

reason

field in the response says

UNAUTHORIZED_CARD

instead of

Incorrect PIN or PIN missing

.

Users of payment devices that use the REST API.

None.

The following support article lists the current issuer response codes that can be used as an alternative for mapping error response reasons for declined transactions:

A defect occurs in our testing environment which causes Merchant-Initiated Transactions and Card-on-File (MIT/COF) Mastercard recurring transaction on FDMS Nashville to have subsequent transactions that fail with the error:

The field is invalid: subsequent_auth_transaction_id

.

Users who test Merchant-Initiated Transactions and Card-on-File (MIT/COF) Mastercard recurring transaction on smartfdc (FDMS Nashville).

None.

None.

A defect has been found that allows merchants who have processed a follow-on credit for a transaction in the Business Center to submit a second follow-on credit for the same transaction.

Users who process payments in the Business Center.

None.

None.

A defect sometimes occurs in the Merchant Specific Velocity Information section of the Case Management Details page. When you click a hyperlink associated with a transaction’s triggered velocity, an error message sometimes appears that says No Records Found.

Users of Decision Manager.

None.

None.

A defect is preventing Merchant Auxiliary Fields from appearing in the Case Management Details page of the Business Center when you use the Microsoft Edge browser.

Users of Case Management in the Business Center.

None.

None.

A defect was discovered when a portfolio user searches for keys in one child account, and then switches to a different account and searches for keys. The results of the second search display the results from the first search.

Portfolio accounts.

None.

Log out of the Business Center and log in again.

A defect occurs when a merchant account sends a Webhooks API request for a list of eligible products for their account. If the account is eligible to receive Invoicing webhooks, the API response returns the Invoicing object; however, the values of the Invoicing

eventTypes

array are missing. The merchant can still subscribe successfully to the Invoicing webhook by referencing the correct Invoicing

eventTypes

field values in the documentation.

Users of the Webhooks API.

The end point is

/notification-subscriptions/v1/products/{organizationId}

.

None.

A defect causes Merchant-Initiated Transactions (MITs) that are requested as incremental authorizations to be sent as partial shipments.

Merchants using Mastercard MIT transactions for incremental authorization and partial shipment transactions.

None.

None.