MX Connect Release Notes

Production Release Date: December 7, 2025

Table of Contents

Table of Contents

1. Features
   • Support for ITIN-Based Onboarding
   • Automated Individual Association for Business Signers
   • Display of Active Equipment for Canadian Merchants
   • International Reporting for Canadian Merchants
2. Enhancements
   • Updated MX Advantage Field Ordering
   • Unified MX Advantage Configuration Logic
   • Consistent Fee Type Output Across Systems
   • Caching Layer for Storage Broker
   • Updated Equipment Experience for Canadian Merchants
   • Compliance Enforcement for Restricted MCCs
3. Bugs and Fixes
   • Redis Memory and TTL Stabilization for WebSocket Messaging
   • Storage Consumer Emitter Reliability Improvements
   • Correct Handling of Encrypted Partner Data
   • Removal of Redundant Crypto Event Persistence

Features

Support for ITIN-Based Onboarding

The platform now supports onboarding individuals and businesses using ITINs as their tax identifier. ITIN validation and masking rules are applied consistently across the UI and backend for all applicable entity types, including LLCs, Partnerships, Sole Proprietors, Government Entities, and Non-Profits.

Automated Individual Association for Business Signers

The business creation workflow now automatically links each signer to an existing individual when matching tax information is found, or creates a new individual record when needed. This ensures every signer receives the correct individual identifier.

Display of Active Equipment for Canadian Merchants

MX Merchant now retrieves and displays all active terminals for Canadian merchants directly from MXM and Stripe. Each device is shown with its serial number, name, and reader type, and appears automatically upon activation.

International Reporting for Canadian Merchants

The merchant view now displays the complete set of Priority International reports—such as Authorizations, Disputes, Funding, and Transaction Activity—while removing U.S.-specific reports and tabs that do not apply to Canadian accounts.

Enhancements

Updated MX Advantage Field Ordering

The MX Advantage setup flow has been redesigned to match the improved layout used in partner-facing tools. Fee Type now appears first, fields are reordered for clarity, and configuration inputs are locked until the user reaches the confirmation step. When surcharge is selected, only card-related fields are shown while ACH-specific inputs remain hidden.

Unified MX Advantage Configuration Logic

The Merchant Facing App now enforces the same rules used across partner flows, including state-specific surcharge restrictions, percentage limits in Colorado, Oklahoma, and Canada, and validation that surcharging is only allowed using the correct billing option. UI and backend safeguards prevent misconfiguration while maintaining compatibility with MXC.

Consistent Fee Type Output Across Systems

Fee Type selections made during MX Advantage configuration now carry through consistently across MXC, the Merchant Facing App, App Engine, and the generated PDF. Restricted-state merchants default to Convenience Fee, and all systems display the final chosen value without mismatches.

Caching Layer for Storage Broker

A Redis-backed caching layer has been introduced to improve read performance. Entity-level caching reduces database load, automatically invalidates stale entries, and gracefully falls back to the database when needed or when caching is disabled.

Updated Equipment Experience for Canadian Merchants

The Equipment tab in MXC now provides a unified view of terminal information sourced from Stripe and MXM. Because terminals appear automatically after activation, no manual add-equipment functionality is needed for Canadian merchants.

Compliance Enforcement for Restricted MCCs

Merchants selecting restricted categories—such as auto, fuel, and fleet—are now automatically prevented from boarding to TSYS. The UI clearly blocks TSYS as an option, backend validation prevents API bypasses, and alternative processors remain available.

Bugs and Fixes

Redis Memory and TTL Stabilization for WebSocket Messaging

A memory issue in the real-time emitter system has been resolved by ensuring all WebSocket routing keys automatically expire after 24 hours and by improving message acknowledgement. This prevents Redis congestion while preserving existing real-time update behavior.

Storage Consumer Emitter Reliability Improvements

A runaway Kafka reprocessing issue causing Redis flooding has been corrected. The update adds structured logging, tighter publish controls, better error handling, and full verification that required Redis keys are created with a 24-hour TTL.

Correct Handling of Encrypted Partner Data

A flaw in cached data handling that resulted in failed decryption and occasional data corruption has been fixed. Sensitive fields now decrypt correctly for users with appropriate access, and non-production keys behave as expected without overwriting valid data.

Removal of Redundant Crypto Event Persistence

The crypto-broker no longer writes decrypted crypto events to the database and instead logs them using the standard logging pipeline. This reduces database load while maintaining audit visibility under existing retention policies.