MX Merchant Release (March 15, 2026)
MX Merchant Release Notes
Production Release Date: March 15, 2026
Table of Contents
Features
Custom Invoice Numbers
Merchants can now enable support for custom invoice numbers through a new setting in the Invoice Settings page. When enabled, invoice creators can enter an alphanumeric invoice number of up to 8 characters during invoice creation. If a custom value is provided, it is stored with the invoice and used throughout related workflows including payment processing, receipts, presentment, and integrations such as email, SMS, and ePay. If no value is entered, the system will continue to generate invoice numbers automatically. Custom invoice numbers cannot be edited or removed once the invoice is created.
Dynamic Tax Identifier Labels
The Portal Information section now dynamically displays the correct tax identifier label based on the identifier used during merchant boarding. Depending on the provided value, the system will display SSN, ITIN, or EIN for beneficial owners, signers, and applicable business entities. Existing masking behavior remains unchanged, and a generic Tax Identifier label will be displayed if the system cannot determine the specific identifier type.
Enhancements
Stripe Vaulted Card Support for Priority International Merchants
Vaulted card functionality has been enhanced to support Stripe card-on-file requirements for Priority International merchants. When a card is vaulted, the system now creates a corresponding Stripe customer and card record. Because Stripe requires a customer email for creation, the merchant must have at least one email address associated with the customer before the card can be vaulted. Each vaulted card now generates two related vault records in the database to support Stripe processing requirements.
Puerto Rico ACH Funding Report
A new ACH Funding Report has been introduced for Puerto Rico merchants, based on the existing report structure used for Priority International Canada. The report captures ACH funding details specific to Puerto Rico merchants. Additionally, the Transactions report has been updated to rename the Province column to Territory to better reflect the regional terminology used in Puerto Rico.
Transaction Query Performance Optimization
Transaction query performance has been improved by limiting the transaction date filter in a key stored procedure to a rolling two-year window instead of scanning the entire historical range. This reduces the amount of data processed during queries, improving execution speed and reducing SQL Server resource consumption as transaction volumes grow. Existing functionality and payment total calculations remain unchanged.
Bugs and Fixes
Transaction Batch Search Refactor
Stored procedures associated with the Transaction Batch table have been refactored to remove their dependency on a full-text index previously used for search operations. Queries were updated to use standard SQL filtering logic while maintaining consistent search results within the Batches view in MX Merchant. This change allows the full-text index to be safely removed without affecting functionality or performance.
Updated 7 days ago