MX Merchant Release (January 18, 2026)
MX Merchant Release Notes
Production Release Date: January 18, 2026
Table of Contents
Features
Dynamic Currency Handling for Terminal Payments
Terminal payment processing has been enhanced for international merchants by dynamically determining the transaction currency based on the merchant’s country. The terminal API now includes the merchant’s country code in the metadata sent to Stripe, ensuring accurate currency selection for each transaction. For example, U.S.-based merchants process payments in USD, while Canada-based merchants process payments in CAD. This improvement ensures correct international payment handling and better alignment with regional requirements.
Enhancements
Node.js Runtime Upgrade for MXM Web
The MXM Web project has been updated to run on a newer Node.js runtime targeting Node 20.x. This upgrade improves long-term platform supportability and alignment with current industry standards. The application has been validated to remain fully deployable and functional across all environments, including QA, UAT, sandbox, and production.
Improved Currency Defaults and Mapping
Currency handling within the Checkout API has been enhanced to ensure consistent behavior across all transaction flows. When a merchant is not part of the Priority International program and the currency code is null, the system now defaults to sending USD instead of a numeric currency code. Additionally, proper currency and country code mappings have been introduced within Checkout to support consistent downstream processing.
At the database level, a default constraint has been added to the CurrencyCode column in the transaction table so that USD is automatically applied when no value is provided. Together, these changes improve reliability and consistency across application and data layers.
Enhanced Payments Report Card Details
The VTX and MX Merchant Payments reports have been updated to improve card detail visibility. For SMS transactions, the Card Type column now displays the network name (such as Interlink), defaulting to Debit when no network ID is present. DM transactions continue to display the card brand (Visa, Mastercard, etc.), with Visa programs always labeled as Visa.
Additionally, the Card Sub Type column now reflects the card level value for both SMS and DM transactions. These enhancements apply only to transactions processed after deployment, with no backfill of historical data.
Bugs and Fixes
Checkout API Stability Improvements
The Checkout API has been stabilized to prevent unhandled runtime exceptions during payment validation failures. The underlying .NET Framework runtime and related modules were updated to eliminate NullReference exceptions that previously caused IIS crashes and HTTP 5XX errors.
With this fix, invalid payment attempts now return a proper 400 ValidationError response instead of triggering server failures. This reduces alert noise, prevents service interruptions, and improves the overall reliability of the checkout flow.
Updated 7 days ago