MX Connect Release (August 18, 2025)

Table of Contents

1. Features

   • MATCH Pro Phase One Release

2. Enhancements

   • Batch Listing API Updates for New Batch View
   • Dormant Account Risk Flag Logic Improvements
   • Risk Job Logging Enhancements

3. Bugs and Fixes

   • Fiserv North Boarding Errors for Government Entities
   • Recurring Reports Date Filter Accuracy
   • Clearing Count Dashboard Widget Corrections
   • Fiserv North Account Number Persistence
   • Low Ticket Risk Flag Missing for US PAY Accounts
   • Passport Account Status Synchronization
   • Missing CYCLE_CAPTURE Events in Passport
   • AWS Migration Configuration Updates for MXC Pods and Passport Callbacks

Features

MATCH Pro Phase One Release

A feature flag has been added to mx-vtx-api-match enabling the service to retrieve responses from MATCH Pro instead of the standard MATCH database when activated. This initial rollout allows production testing of MATCH Pro credentials and endpoints while ensuring existing functionality remains unchanged when the flag is disabled. Additional updates include regex and field length adjustments to comply with MATCH Pro requirements. This release establishes the foundation for a full transition to MATCH Pro in the next phase.

Enhancements

Batch Listing API Updates for New Batch View

The Batch Listing API in Passport has been updated to align with the requirements of the new batch view. Changes include endpoint modifications, request/response structure updates, and expanded data retrieval capabilities. These updates ensure the UI can present all required batch details per the latest design specifications, supporting enterprise clients such as Omnna in processing card transactions through PCE APIs and Passport UI.

Dormant Account Risk Flag Logic Improvements

The dormant account risk flag logic has been re-implemented and refined to trigger only after 60 consecutive days without transaction authorizations, preventing active accounts from being incorrectly flagged. Key updates include:

• Switching to settlement reports as the data source instead of authorization/decline counts
• Coverage across First Data, TSYS, and Fiserv North entities
• Consolidated query logic for improved efficiency
• A new global cap to separate past 60-day inactivity from daily sales and refunds

These changes improve flag accuracy and ensure consistent application of dormancy rules.

Risk Job Logging Enhancements

Detailed per-account calculation logging has been added to production risk jobs to address performance degradation issues. The enhanced logs now capture each risk rule evaluation in addition to query and data-fetch stages, enabling faster bottleneck identification and root cause analysis. This improvement increases visibility into execution flow and aids in proactive system performance monitoring.

Bugs and Fixes

Fiserv North Boarding Errors for Government Entities

Resolved boarding issues for Fiserv North involving government-related merchant profiles. Updates include:

• Correctly applying the “G – Govt. Entity” flag for government merchants to prevent SPARK Exclusion Indicator errors
• Adjusting Pricing Type for MCC Code 9222 to “034 – Court/Fines/Govt Serv.”

These corrections ensure eligible government merchants can be approved and boarded without triggering validation errors.

Recurring Reports Date Filter Accuracy

Fixed an issue where recurring reports failed to return accurate results for predefined and custom date ranges such as “This Week,” “This Month,” “Last 7 Days,” and “Last 30 Days.” The export functionality is now aligned with the filtering behavior on the recurring grid, ensuring data consistency across retrieval and exports.

Clearing Count Dashboard Widget Corrections

The Clearing Count dashboard widget in MXC has been updated for improved accuracy:

• TSYS Gross Clearing Count now uses batchDate instead of achPostingDate
• Fiserv North Gross Clearing Count now references daily data from Reporting > Fiserv - North > Clearing > Daily instead of monthly data

These changes ensure daily clearing volumes are represented correctly, with regression testing confirming no impact to related dashboard metrics.

Fiserv North Account Number Persistence

Fixed an onboarding issue where Fiserv North account numbers were not being saved to the database due to API delays or retries. The update ensures account numbers are consistently generated, stored, and displayed in the UI, even during 504 timeout events.

Low Ticket Risk Flag Missing for US PAY Accounts

Resolved a defect where the Low Ticket Risk flag was not populating for certain US PAY accounts in MXC due to missing scoring data. The fix ensures the score field is populated for all eligible accounts, restoring accurate abnormal ticket detection and improving fraud visibility.

Passport Account Status Synchronization

Addressed discrepancies in account status display across MX Connect screens. The processor’s banking tab is now the single source of truth for funding and billing account details, ensuring the Passport tab and processor banking tab remain perfectly synchronized.

Missing CYCLE_CAPTURE Events in Passport

Corrected an issue where CYCLE_CAPTURE events were occasionally missing in Passport due to Kafka processing lag. The acknowledgment process now confirms successful processing before marking messages complete, ensuring no data loss and allowing for precise recovery in case of delays.

AWS Migration Configuration Updates for MXC Pods and Passport Callbacks

Applied AWS-specific configuration updates for MX Connect pods and Passport callbacks in both sandbox and production. New .yaml environment files were added for mx-vtx-consumer-ach-funding-data and mx-vtx-consumer-cycle-data services, ensuring proper callback routing and uninterrupted data flow in the AWS environment.