MX Merchant Release (April 12, 2026)
MX Merchant Release Notes
Production Release Date: April 12, 2026
Table of Contents
Features
Enhanced Payment Notifications with Invoice Details
Enhanced payment notifications to include detailed invoice information, providing recipients with clearer context about their transactions directly within email communications.
Enhancements
Updated TapTrans Settlement File Format for MasterCard
Updated the Fiserv Omaha TapTrans settlement file format for MasterCard by expanding the Unit Measure Code field and adjusting subsequent field positions to align with TapTrans 038 specifications, ensuring successful validation without impacting non-MasterCard processing.
Refactored Card Vaulting Flow for Improved Stability
Refactored the card vaulting flow to use a reliable merchant identifier instead of customer-based mapping, resolving issues caused by customers associated with multiple merchants and restoring stable Stripe vaulting functionality for both global and non-global merchants.
Updated Invoice SMS Messaging for Merchant Branding
Updated invoice SMS messaging to remove MX Merchant branding and ensure communications appear merchant-branded, while preserving functionality such as access codes, opt-out instructions, and dynamic links, providing a more consistent and clear customer experience.
Enhanced Valor Reconciliation Report
Enhanced the MX Merchant Valor reconciliation report to separately summarize SMS PIN Debit and credit card deposits for eligible merchants by introducing Debit Deposits and Credit Deposits line items, driven by merchant entitlement and updated query logic, while preserving the existing single total for merchants without PIN debit enabled.
Bugs and Fixes
Resolved MXM Payment Filter Issues
Fixed an issue where MXM payment filters were not functioning correctly by addressing underlying data and default value handling, ensuring accurate filtering of payment records in the UI.
Corrected Refund Status Handling for Vortex Transactions
Fixed an issue where declined refunds from Vortex were incorrectly marked as successful by removing override logic for Vortex-processed transactions, ensuring refund statuses accurately reflect network responses while preserving existing behavior for legacy payment flows.
Fixed Refund Failures After Rapid Refund Attempts
Fixed an issue where invoice and recurring refunds could fail after a rapid refund due to incorrect paid amount calculations by updating the validation logic to include only approved transactions, ensuring refunds process correctly once the merchant account is unlocked.
Corrected Processor Assignment for Downline Partners
Fixed an issue where processorName and processorPlatform were not correctly set to Priority for downline partners, ensuring accurate population of merchant.account and merchant.processor records during boarding across multi-level partner hierarchies.

Updated 22 days ago
