MX Connect Release (September 1, 2025)

Table of Contents

1. Features

   • MXC and Keycloak Parallel Authentication
   • Entity API Updates for PACE
   • Passport Consumer Product Integration API
   • Passport Integration Dedup Consumer

2. Enhancements

   • Feed Notifier Error Handling Improvements
   • API Automation and Bot Task Runner Config Updates
   • Orchestration Image Path Updates for AWS
   • API Boarding Config Updates
   • AppEngine QA Environment Link Fix
   • AWS Sandbox Config File Consistency
   • MySQL Connection Pool Logging

3. Bugs and Fixes

   • Bank Account Update Errors with Multiple Processors
   • Reserve Addition Error for Fiserv North

Features

MXC and Keycloak Parallel Authentication

The authentication system has been enhanced to support a parallel migration to Keycloak while maintaining backward compatibility with MXC authentication. A new user-level flag, isUserKeycloakMigrated, determines whether a user is authenticated with MXC (legacy) or Keycloak (migrated).

Key updates include:

• Conditional routing of backend API logic across authentication, user management, invitations, and password handling
• Two independent UI deployments (MXC and Keycloak) for a smooth, phased transition
• No disruption for existing users during the migration

This release enables production testing of Keycloak integration while preserving current functionality.

Entity API Updates for PACE

The Entity API has been aligned with PACE requirements for creating individuals during progressive onboarding. Changes include:

• Addition of an optional externalId field alongside platform
• Removal of fundingAccounts and unitedStatesCitizen as required fields

These updates ensure consistency with PACE and streamline entity creation flows.

Passport Consumer Product Integration API

The Passport Integration API now supports individual integrations through the Product Integration API, enabling account creation for individuals. Errors are logged in syslogs for improved traceability. Case creation will be delivered in a separate update.

Passport Integration Dedup Consumer

The Dedup Consumer has been enhanced to support Passport integration for individual entities, improving identity management across the system.

Enhancements

Feed Notifier Error Handling Improvements

Error handling in mx-vtx-consumer-feed-notifier has been improved by wrapping asynchronous HTTP calls in try/catch blocks. This prevents unhandled failures that previously caused Level 60 errors, reducing error frequency and improving reliability without altering existing functionality.

API Automation and Bot Task Runner Config Updates

Configuration updates have been applied to mx-vtx-api-automation and pps-eventing-bot-task-runner to meet the latest environment and automation requirements. These updates ensure consistency across both repositories.

Orchestration Image Path Updates for AWS

All entity definitions have been updated to remove hardcoded image paths and nsxTags, ensuring deployments now pull container images directly from ECR instead of Artifactory. This improves alignment with AWS best practices.

API Boarding Config Updates

The sandbox AWS config file for api-boarding has been renamed to aws-nv-sandbox.yaml, with updated endpoints for Merchant Portal, Pipe, and Role APIs. This ensures proper alignment with the sandbox environment configuration.

AppEngine QA Environment Link Fix

The AppEngine Integration link in QA was previously pointing to the aws-nv-sandbox environment. The link has been corrected to route to the QA environment, ensuring accurate navigation during AppEngine integration management.

AWS Sandbox Config File Consistency

All aws-nv-sbox.yaml config files across affected services have been renamed to aws-nv-sandbox.yaml, improving consistency and alignment with sandbox environment naming standards.

MySQL Connection Pool Logging

MySQL connection pool logging has been added to the Storage Broker to monitor KnexJS pool usage. Metrics are now available in Kibana dashboards, improving visibility into connection contention and simplifying performance troubleshooting.

Bugs and Fixes

Bank Account Update Errors with Multiple Processors

Resolved an issue where merchants using multiple processors (e.g., Fiserv North, TSYS) could not edit or save funding accounts, receiving a “Cannot edit funding accounts” validation error. Banking tab updates will now save successfully without errors.

Reserve Addition Error for Fiserv North

Fixed an issue in MXC Enterprise where adding a reserve percentage on the Fiserv North → Reserve tab resulted in an “Unknown error occurred.” Users can now successfully create and save reserve amounts.