MX Connect Release (August 4, 2025)
Table of Contents
Features
Automated Stripe Onboarding for Merchants
MXC now offers end-to-end Stripe integration during merchant onboarding. Upon submission of required documentation—such as ID verification, selfies, and proof of address—Stripe accounts are created and linked to merchant profiles automatically. The system enforces document validation, integrates MFA for review and signature, and populates the Stripe Global Account ID upon successful submission, providing seamless activation of payment capabilities.
New Partner Types and ID Mapping for Passport
The platform now supports new partner types—ISV and Priority Tech Ventures—for Passport. These partner types follow tailored onboarding, billing, and hierarchy rules, ensuring accurate attribution of fees and revenue share. Additionally, partners can now input Program Manager IDs and Customer IDs during onboarding. This enables detailed customer-level billing, revenue share reporting, and improved statement transparency.
Canadian Routing Support and Application Enhancements
Support for Canadian routing numbers has been added to the banking configuration for Global product onboarding. The system now automatically maps routing numbers to their corresponding bank names. Additionally, new delivery modes have been added to the Canadian application flow, allowing users to send applications for completion and/or signature. All Canadian-specific fields—such as tax IDs and phone formats—are fully supported, ensuring compliance and user clarity.
Webhook Support for Stripe Chargebacks
The platform now listens for charge.dispute.created webhook events from Stripe. When a dispute is triggered, the system automatically reverses the original payment intent and initiates a return transfer. This ensures accurate and timely reconciliation of disputed funds, enhancing financial accuracy for merchants on the Stripe platform.
Enhancements
Expanded Orchestration Support for Individuals
A new orchestration entity has been introduced to support individual-level workflows. The platform now includes dedicated data storage (MySQL, Elasticsearch, Kafka) for individual records, syncing data from personal accounts and entities. This enables improved onboarding, orchestration, and reporting for individuals alongside traditional businesses.
Improved API Behavior for PUT Requests
The account update API has been enhanced to return the entire updated payload rather than just the ID, improving developer usability and eliminating redundant fetch calls. Additionally, the system now properly enforces read-only field validation—attempts to update system-managed fields like acl, created, or platform now result in a 400 Bad Request, maintaining data integrity.
Improved Duplicate EIN Banner Flow
When a merchant with an existing EIN is onboarded, the system now stores user preferences before proceeding with account setup. This prevents redundant banner displays and ensures a smoother user experience during Passport onboarding, avoiding confusion and duplicate data entry.
UBF Billing Schedule Flattening for Passport
UBF generation has been reworked to flatten agreement and billing schedule structures, allowing for transaction-level visibility and tiered pricing models. Pricing can now be calculated based on transaction volume, customer count, and program details—enabling precision billing and granular reporting downstream.
Configurable Revenue Share Skipping
MXC now offers a toggle to bypass billing and revenue share for specific partners during onboarding. This allows internal retention of 100% revenue while still generating reports and applying upstream billing to higher-tier partners, offering flexibility in managing strategic partnerships.
Updated Enterprise API Configurations
Both Production and Sandbox environments have been updated to route Enterprise UI traffic through the correct AWS API endpoints. This ensures accurate environment separation, improved routing stability, and a consistent development and testing experience across all tiers.
Bugs and Fixes
Filter Errors in Card Payments Reporting
A defect that blocked filter functionality in the Card Payments report has been resolved. Users can now filter by transaction type, card type, merchant number, and location in both Sandbox and Production. The root cause was traced to risk-report filters unintentionally affecting general reports; this logic has now been isolated appropriately.
Sponsor Bank Toggle Not Working
A recent issue prevented users from enabling the Sponsor Bank option when configuring App Engines. This toggle is now functioning correctly across all environments, ensuring Synovus and other TSYS banking configurations are fully supported during onboarding.
Invisible Onboarded Merchants in QA
In the QA environment, newly onboarded merchants were not appearing in the Applications or Clients grids due to Redis client incompatibility. The issue has been resolved by reverting to a previous consumer version, restoring visibility without requiring code changes.
Bank Info Save Failures
Validation issues in the banking information form caused account updates to fail due to missing fields. A script was executed to restore required sponsor field values, and validation logic has been corrected to ensure that future updates are processed successfully.
Case Grid Grouping Crash Resolved
Attempting to group cases by assignee in the ACH Rejects Handling and Cases grids previously caused the application to crash. This issue has been fixed, and additional case columns—such as status, assignee, and open/close dates—are now available for sorting and filtering, enhancing usability for finance users.
OFAC CSP and CORS Errors Fixed
Connectivity issues with LexisNexis Trunarrative services caused by outdated Content Security Policies and CORS configurations have been resolved. Updated policies now support secure communications with external services, restoring expected functionality for OFAC outcomes and approvals.
Updated 23 days ago