MX Connect Release Notes

Production Release Date: November 9, 2025

Table of Contents

1. Features
   • New SMS Fee Reports Added to MXC Reporting
2. Enhancements
   • Surcharge Option Display for Canadian Merchants in MX Advantage
   • Priority International Reports Reordered Alphabetically
   • EFT Report Updates and Adjustments
   • Funding Report Renaming for MXC and MXM
   • Optimized MX Connect Audit Data Processing
   • Simplified Crypto Event Tracking via Logging
   • Removal of Dedup Callback Streamliner
3. Bugs and Fixes
   • Corrected Merchant Settlement Delay Updates
   • Resolved SMS ACH Funding Report Data Load Issue

Features

New SMS Fee Reports Added to MXC Reporting

Three new reports have been added under MXC Reporting → Priority VTX → SMS Billing Reports to enhance transaction visibility and analysis:

• Daily Visa SMS Fee Report: Displays Visa and Interlink transaction details, including location, account, amount, transaction type, reference number, FPI, fees, and date.
• Daily Non-Visa SMS Fee Report: Provides Non-Visa transaction data with searchable and sortable columns for location, account, reference, network, amount, and fees.
• Monthly Non-Visa SMS Fee Report: Summarizes Non-Visa SMS fees monthly with searchable fields such as location, account, network, count, amount, and transaction date.

All reports support advanced filtering and sorting for efficient billing and reporting workflows.

Enhancements

Surcharge Option Display for Canadian Merchants in MX Advantage

In MX Advantage, merchants processing Canadian transactions will now only see the Surcharge option. The Convenience Fee, Service Fee, Admin Fee, and Cash Discount options have been hidden to ensure compliance and simplify fee configuration.

Priority International Reports Reordered Alphabetically

The Priority International Reports link in MXC has been moved to align alphabetically within the Reports section, providing a more consistent and intuitive navigation experience.

EFT Report Updates and Adjustments

The EFT Report in MXC has been updated to fix sorting issues in the Merchant and Bank Name columns and restore full filtering functionality. Additionally, the column label “Bank Number” has been renamed to “Bank” for improved clarity and consistency across reports.

Funding Report Renaming for MXC and MXM

The EFT Report has been renamed to “Funding (EFT)” in both MXC and MXM. This update makes the report name more intuitive and user-friendly, particularly for users less familiar with EFT terminology.

Optimized MX Connect Audit Data Processing

Audit data processing for MX Connect has been optimized by removing reliance on the MySQL auditor table. Data now writes directly to ElasticSearch through esDirectCompute, improving performance and maintaining full compatibility with Notifier, Feed Consumer, and other existing consumers without any data loss.

Simplified Crypto Event Tracking via Logging

The crypto-broker service has been updated to replace database persistence for crypto events with log-based tracking. Events are now captured through system logs under a 90-day retention policy, reducing RDS storage usage while maintaining audit compliance and operational visibility.

Removal of Dedup Callback Streamliner

The dedup callback streamliner and related persistence have been fully removed from orchestration. This cleanup eliminates unused pipeline components and database writes, reducing system complexity while maintaining stable entity update flows and orchestration performance.

Bugs and Fixes

Corrected Merchant Settlement Delay Updates

Resolved an issue where merchant settlement delay days were incorrectly reset to 1 day after post-boarding updates on the Fiserv processor. The webhook process now correctly preserves the Risk-approved delay days value, ensuring accurate settlement timing and consistent merchant cash flow.

Resolved SMS ACH Funding Report Data Load Issue

The Deposit Date column has been removed from the SMS ACH Funding Report to address data load failures caused by missing companyDescriptiveDate values. Following deployment and reindexing, data now loads correctly through Kafka without requiring this field.