MX Connect Release (July 21, 2025)

Table of Contents

1. Features

   • Merchant Status Update on LexisNexis Verification Expiry
   • Standardized Pending Category (Reason) Codes for Underwriting
   • Individual Entities and Accounts Support

2. Enhancements

   • Approved Monthly Volume Update Script Execution
   • Pricing Template Name Validation Fix
   • AWS Configuration Consistency Validation
   • ACH Rejects Report Improvements
   • Internal APIs Enhanced for Individual Boarding

3. Bugs and Fixes

   • Removal of Obsolete Risk Flags

Features

Merchant Status Update on LexisNexis Verification Expiry

A new consumer service, mx-vtx-consumer-lexis-nexis, was introduced to monitor changes from LexisNexis Idverse and automatically update merchant account statuses based on KYC link activity. When a verification link expires or all KYC responses are finalized, the processor status now correctly transitions to Under Review and displays the expired link with options to resend. Upon regenerating the link, the status automatically updates to Received, ensuring account queues accurately reflect current states and remain clean.

Standardized Pending Category (Reason) Codes for Underwriting

The underwriting process was enhanced by implementing a standardized Pending Reason Code system. Users can now tag applications with categorized reasons directly within the Processor tab using a searchable, multi-select dropdown. Selected reasons appear as individual tiles for clarity. Additional improvements include an MCC Code filter in the Clients Grid and export enhancements that add MCC Code, Pending Reasons, and last status update timestamps. These changes improve underwriting visibility and decision-making efficiency without altering user permissions.

Individual Entities and Accounts Support

The orchestration platform now supports individual boarding workflows with the addition of new entities and API capabilities:

• Individual_Entity: Full schema definitions added to MySQL, Elasticsearch, and Kafka, capturing identity, contact info, citizenship, funding accounts, and audit metadata.
• Individual_Account: Dedicated orchestration entity for managing individual accounts, with full lifecycle management APIs.
• BoardingDedupProducts lookup updated with an allowsIndividuals flag to configure product eligibility for individual entities and accounts.

These enhancements enable comprehensive onboarding and management of individuals alongside business entities.

Enhancements

Approved Monthly Volume Update Script Execution

A production script was executed to update the Approved Monthly Volume field under the Exceeded Monthly Volume risk flag for a predefined set of merchants. The update logic applied the higher value between each merchant’s 120-day average volume and their existing approved volume. Only merchants listed in the approved dataset were modified. Validation confirmed no changes to unaffected merchants and no disruption to the risk flag’s functionality, improving volume-based risk accuracy.

Pricing Template Name Validation Fix

The pricing template validation logic was updated to use exact name matching rather than regular expressions. This fix resolved an issue where users were incorrectly prevented from renaming pricing templates due to false-positive conflicts. The change allows users to rename templates as expected while still preventing duplicate names for the same product and domain.

AWS Configuration Consistency Validation

The Vortex WS Migration initiative reviewed AWS configuration files across develop and master branches for targeted services. Repositories with missing AWS config files in master were identified, and pull requests were created to backfill missing configurations. This ensures consistent AWS environment configurations across branches, supporting smoother deployments.

ACH Rejects Report Improvements

Several enhancements were made to the ACH Rejects reporting and handling modules:

• Additional Case Data Columns: Case Status, Case Assignee, Case Open Date, and Case Closed Date were added to the ACH Rejects grid to aid finance users in resolving rejects.
• Date Alignment: Received and transaction dates were aligned with sponsor reports, with standardized formatting excluding timestamps and time zones.
• Inclusion of ACH.com Data: ACH.com reject data now appears correctly in the reject handling grid, based on the DateEntered field rather than creation timestamp.
• Removal of Item Cap: The 10,000 record limit on reject reports was removed to allow full data retrieval for up to six months, with improved API tracking for total hits.

These improvements enhance accuracy, completeness, and usability of ACH rejects data for financial teams.

Internal APIs Enhanced for Individual Boarding

The Internal Entity and Internal Account APIs now support full lifecycle management for individual onboarding, including create, retrieve (single and bulk), update, delete, pagination, filtering, and sorting. These secured endpoints include field validation, error handling, and updated Swagger documentation and Postman collections. These updates streamline individual entity and account operations and improve API usability.

Bugs and Fixes

Removal of Obsolete Risk Flags

Four outdated risk flags—Keyed Percentage, Average Ticket, Multi BIN, and Duplicate Cards—were removed from MXC’s risk monitoring framework. This change reduces job failures and streamlines risk processing. The remaining risk flags and associated features such as scoring, review screens, label attachment, search, and filtering continue to function normally without disruption.