Known Issues

A defect occurs in our testing environment that causes Merchant-Initiated Transactions and Card-on-File (MIT/COF) Mastercard recurring transactions on FDMS Nashville to have subsequent transactions 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 transactions on 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.

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.

A defect was discovered that sometimes prevents a customer email address from displaying in the Transaction Details page of the Business Center. This happens when the email address is entered with upper-case letters. A future update will ensure that email addresses are not case-sensitive.

Users of Transaction Details.

None.

None.

A defect was discovered that causes some authorization requests for merchant-initiated transactions that use tokenization

and

that are older than 60 days to fail to settle. Until the defect is fixed, a new authorization is required to regenerate the token.

Merchants in India.

This issue occurs when a merchant-initiated transaction is sent that includes an authorization and capture but does not include this API field in the payload:

REST API:

processingInformation.authorizationOptions.initiator.credentialStoredOnFile

Simple Order API:

subsequentAuthFirst

SCMP API:

subsequent_auth_first

Consequently, the authorization component of the transaction succeeds, but the capture fails. We will update our system to ensure that the authorization fails when the API field is not present.

When you send a merchant-initiated transaction that includes an authorization and capture, be sure to include the API field in the payload.

A defect was found that causes some report replays for Decision Manager to display the error "Data not found."

Users of Decision Manager who request report replays.

This error occurs when the report has not finished regenerating.

Ignore the error and try again in a few hours.

A defect was discovered that causes RTSS messages for authorization reversals (

payments.reversals.accept

) to lack the

originalSystemTraceAuditNumber

field for American Express transactions.

Users of RTSS.

None.

None.

A defect was discovered that prevents the Export Merchant List from working in the legacy version of Manage Merchants in the Business Center. The message “The file is not available, please try again later” displays.

Users of portfolio accounts.

None.

None.

A defect was discovered that sometimes happens to Electronic Funds Transfer at Point of Sale (EFTPOS) transactions. When the month of a card's expiration date is December, the expiration year sometimes increments by one, causing transaction failure.

Users of EFTPOS.

The root cause is a setting in the code that uses YYYY (week year) instead of yyyy (calendar year).

None.

A defect was discovered that creates two issues:

Some customer email addresses are not displaying in the Transaction Details page of the Business Center.
Searching transactions by email sometimes does not display all transactions associated with that email address.

Users of Transaction Search and Details.

None.

None.