MX Merchant Release Notes

Production Release Date: December 21, 2025

Table of Contents

1. Features
2. Enhancements

Features

Improved MXM Availability During MXC Outages

MX Merchant authentication and merchant location switching now operate independently of MXC availability. Users can log in, switch merchant locations, and continue processing payments in MXM even when MXC is unavailable, providing a more resilient and uninterrupted experience.

Priority Global Currency Configuration Update

Currency handling for Priority Global merchants has been enhanced to remove the hardcoded default currency. MXM now derives the transaction currency from the merchant’s country configuration (CAD for Canada, USD for the United States), validates currency prior to submission, and includes the merchant country code when sending transactions to Vortex to ensure accurate processing.

Enhancements

Duplicate MXM Merchant Account Prevention

An issue that could result in duplicate MXM merchant accounts during the boarding process has been resolved. When the MX Merchant product is added and removed multiple times, older in-progress accounts are now automatically canceled so that only the most recent account remains active and available for approval.

Accurate Payments Grid Totals and Exports

The MXM Payments grid has been corrected to ensure calculated totals and exported data accurately match the transactions displayed when filters, including Customer source, are applied. This update ensures consistent reporting and reliable reconciliation.

Correct AMEX Void Synchronization with Passport

Void processing for American Express transactions has been improved to ensure proper synchronization between MXM and Passport. Responses indicating “Reversal accepted” are now correctly treated as approved, allowing original sale transactions to update accurately to a voided or reversed state and maintaining consistency across systems.

Terminal Surcharge Label and Rate Capture

Surcharge labels and rates for terminal transactions are now correctly captured and stored. Surcharge details are passed through the terminal API and saved from Stripe metadata, enabling accurate display of surcharge information within MX Merchant payment details.