MX Merchant Release (May 12, 2025)
Production Release Date: May 12, 2025
Table of Contents
Features
Improve MXM Performance When Modifying Between Locations
Improved performance when switching locations in MXM by updating the Control Owner feature logic. The system now avoids unnecessary retries on client-side (4xx) errors and only attempts to update the control owner if the user is associated as a control person in MXM.
Enhancements
Username in MXM and Passport Should Be Same for SSO to Work
To ensure seamless SSO between MXM and Passport for SMB merchants, Passport usernames will now be aligned with the corresponding MXM admin usernames (not emails) linked to the control owner. A script will also be implemented to update existing Passport records accordingly.
Control Owner - MXM Banner Appearance - API Changes
The MXM application now dynamically displays the control owner banner based on the user's role per merchant account. The banner will only appear for users marked as active control owners, and visibility will update appropriately as users switch between accounts.
Terminal - MXM - Stripe Terminal Onboarding - Proxy API to Call Stripe
Added support for Stripe Terminal onboarding via the mx-merchant-api-proxy, enabling proxy API calls to Stripe for creating, listing, retrieving, updating, and deleting terminal-related entities such as Locations, Configurations, and Readers. This includes secure outbound connectivity, JWT-based authentication, and dynamic Stripe location creation based on MXM merchant data.
Bugs and Fixes
MXM Payments Report Does Not Have the Network Message Visible
Resolved an issue where network messages were not populating in the MXM Payments Report by correcting the mapping of network audit members. The requestData field is now properly mapped to request in netAudit, enabling accurate message details for checkout v3 payments.
Updated 23 days ago