MX Merchant Release (January 16, 2024)

This release includes the following adjustments:

Fixed: Issues linked to decelerating API performance

Card Account Token

The Checkout/cardaccounttoken endpoint, responsible for making payments from the customer details screen using a vaulted card, experienced slow API calls, taking more than 25 seconds to process. We have successfully resolved this issue, and the cardaccounttoken no longer appears on the expensive queries list.

Broadcast

The Checkout/broadcast endpoint, utilized for delivering messaging upon a user signing into MX Merchant, faced uncharacteristically slow performance, with API calls taking more than 25 seconds to process. We are pleased to report that these issues have been addressed, and calls to this endpoint are now performing optimally.

Fixed: MX Express card present mismatch error

In the "Advanced Settings" tab on MX Express for card present transactions, configurations previously needed to be set for MX Express to ask the application before presenting a payment type. This option was only available if the merchant decided to key in transaction information manually.

In this sprint, significant improvements have been made. Now, when a merchant in MX Express selects a card not present transaction and inserts a card, an error message will not be displayed. Instead, the card will be processed as a "card present" transaction.

Fixed: Validation errors from Transaction, Batch, and Chargeback Reports

Users encountered validation errors when attempting to access Transaction, Batch, and Chargeback reports, preventing access to vital information. We are pleased to confirm that these errors have been resolved, and users can now seamlessly access and utilize the reports as intended.

Fixed: MX Express meta field issue

A critical issue was identified where memos added to payments in MX Express were not appearing in MXM when reviewed in the payments grid. Fields such as "MetaField," "Invoice," "Memo," "Customer Number," and "Customer Name" were not being populated.

We're happy to announce that this issue has been successfully resolved. MX Express users can now view the data associated with the mentioned fields in the payments grid.

Fixed: Keyclock 2FA settings changing without input

An issue was discovered where a user's two-factor authentication settings were inadvertently altered when adjusting user settings or linking a user to a new merchant in MX Connect.

We're pleased to confirm that this issue has been fixed. Two-factor authentication settings will no longer be impacted by changes to user settings or linking a user to another merchant.