Known Issues

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.

None.

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

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.

A defect occurs in the Business Center when you navigate to

Account Management > Billing

. The message at the top of the page says “paymyinvoice.currencyAlert” instead of “Supported Invoice payment currency - USD, CAD, GBP & EUR”.

Users of Billing in the Business Center.

None.

None.

A defect causes some card-present transactions with a failed PIN entry to receive the error message “Decline - Inactive card or card not authorized for card-not-present transactions.”

Users of in-person card terminals.

None.

None.

A defect was discovered that occurs when you search for

Transactions by Phase > Authorizations Ready to Settle

, submit those transactions for capture, and then submit them again while they are processing. Doing this causes duplicate transactions.

Global.

None.

Wait until capture requests are finished and do not resubmit them.