MX Connect Release (February 1, 2026)
MX Connect Release Notes
Production Release Date: February 1, 2026
Table of Contents
Features
Priority International Multi-Processor Configuration
The Priority International product now supports configuration by processor, country, and currency during merchant setup and onboarding. Merchants can be configured with supported combinations such as Stripe with Canada and CAD for Canadian merchants, and Stripe with USA and USD for Puerto Rico merchants. This establishes the foundation for future multi-currency and multi-processor support across international markets.
Enhancements
Asynchronous PDF Generation for Signature Workflow
The Signature API has been enhanced to offload PDF generation to AWS Lambda, replacing the in-process Puppeteer and Chromium workflow. PDF generation now runs asynchronously with persisted job metadata for tracking, retries, and error handling, improving system stability and reducing memory usage while preserving the end-to-end HelloSign signing flow.
Merchant Agreement PDF Updated with Terms and Conditions
The Canadian merchant onboarding flow has been updated so that generated Merchant Agreements now include the full terms and conditions appended to the document. This ensures pricing details are securely included and accurately reflect merchant pricing configured in MXC without reliance on a public website.
Improved Funding Webhook Reliability
Funding event consumers have been enhanced with configurable retry logic when sending messages to the Passport webhook. Using a feature-flagged approach, failed requests caused by transient network issues are now retried with a backoff strategy, improving resilience and preventing temporary failures from resulting in permanent processing issues.
Fiserv North Authorization Reporting Accuracy
Fiserv North authorization reporting has been improved to filter out records with card type values representing batch totals rather than true authorization events. This update improves reporting accuracy while preserving existing decline, risk, and settlement calculations.
Bugs and Fixes
Expanded Transaction and API Validation Handling
Several updates have been made to improve transaction processing and API consistency. Valid TSYS sales transactions reported with supported transaction codes and card types are now correctly processed and forwarded for settlement visibility. The Location PUT API now returns a response body to align with standard API behavior, validation restrictions limiting entities to a single product type have been removed, and Location API validations have been enhanced to better support Passport-based integrations while maintaining backward compatibility.
Updated 23 days ago