MX Connect Release (January 18, 2026)
MX Connect Release Notes
Production Release Date: January 18, 2026
Table of Contents
Features
Merchant-Level Same Day ACH Configuration
Merchant-level control for Same Day ACH funding has been introduced in MXC for TSYS merchants. Admin, Domain Admin, and Implementation users can now selectively enable or disable Day 1 funding for individual merchants, while keeping it disabled by default for all others. The configuration is available within Merchant Funding Configuration, includes clear risk messaging, syncs settings to TSYS, enforces role-based access controls, and records all changes in audit logs. This enhancement reduces portfolio-wide funding risk while supporting Day 1 funding requirements for eligible merchants.
Enhancements
Improved Error Monitoring and Diagnostics
Sentry has been integrated into the MXC UI to enhance error monitoring and diagnostics. The implementation is gated behind a Statsig feature flag, allowing observability to be safely enabled or disabled as needed. This controlled rollout approach minimizes performance and regression risks while improving visibility into UI errors.
Enhanced Stripe Error Visibility
Stripe integration has been enhanced to propagate detailed Stripe error messages and response information through the API and into the MXC UI. Users now see actionable Stripe feedback directly in the interface instead of generic error messages, enabling faster troubleshooting and clearer insight into onboarding and transaction failures.
Improved MXC UI Caching Strategy
The MXC UI caching strategy has been improved to ensure users consistently load the latest version after deployments. Caching has been disabled for HTML and other non-hashed assets, while long-term immutable caching remains enabled for hashed JavaScript, CSS, and static assets. This change reduces stale UI issues, prevents 404 errors caused by outdated cached files, and maintains optimal performance with no impact to 2FA login behavior.
SMS Billing Report Transaction Count Improvements
SMS Billing Reports have been updated to support a future transition of transaction count values from string to integer while maintaining backward compatibility with existing production data. The reporting API, orchestration, and UI now safely handle string-based values without errors and are prepared to support numeric aggregation and filtering once integer storage is enabled. This ensures reports continue to load reliably today and fully support enhanced reporting capabilities in the future.
Bugs and Fixes
Alien Registration Card Validation Fix
Validation for Alien Registration Card secondary identification has been corrected to accept alphanumeric values shorter than eight digits. Valid values ranging from seven to nine characters now sync correctly without triggering validation errors, aligning system behavior with Passport rules and ensuring successful customer creation and mapping.
Risk Filter Consistency Fix
An issue was resolved where previously saved risk filters returned different hit counts compared to manually configured filters. The fix restores consistent risk evaluation logic so saved filters now evaluate scores and criteria identically to manual selections, ensuring reliable and accurate risk monitoring.
Updated 23 days ago