MX Merchant Release (February 15, 2026)
MX Merchant Release Notes
Production Release Date: February 15, 2026
Table of Contents
Features
Multiple Stripe Platform Account Support
Enhanced the Stripe integration to support multiple Stripe platform accounts, enabling transaction processing across Priority Commerce Canada, Priority Technology Holdings, and future regional platforms. This update ensures successful merchant onboarding, accurate reporting, and reliable card-present and card-not-present processing, while enforcing immutability of the merchant country field after boarding.
SMS Batch Report Availability in MXM
The SMS Batch Report is now available in MXM, providing clients with visibility into SMS batches processed by Priority that are not reported via TSYS or First Data. Report data aligns with MXC records and includes batches with a status of “funded” (previously “settled”), with access restricted to authorized clients.
SMS Transactions Report Availability in MXM
The SMS Transactions Report is now available in MXM, giving clients full visibility into SMS transactions processed by Priority that are not reported via TSYS or First Data. Data aligns with MXC to ensure accuracy and consistency, and access is restricted to authorized clients to support contractual reporting requirements.
JWT Support in MXM Checkout
Implemented hybrid authentication in the MXM Checkout pipeline to support JWT validation. Incoming Keycloak JWTs are validated against the configured JWKS endpoint and securely exchanged for internal MXM AccessTokens before request processing. Legacy AccessToken and Basic Auth traffic continues to function unchanged, while invalid or expired JWTs return a 401 Unauthorized response.
Automatic Partner User Linking for Enterprise Merchants
Enhanced merchant boarding to automatically create or link a partner user when an Enterprise merchant’s MXM product is approved. Upon approval, the system creates a user using the partner domainId as the username or links an existing user to the newly created merchant when at least one feature is enabled. No action is taken for other product statuses.
Enhancements
Re-enable Cash and Check Payment Methods for Canadian Merchants
Re-enabled cash and check payment methods for eligible Canadian merchants to support specific payment requirements. This reverses the previous global restriction in MXM and restores the ability to accept non-card payment types during onboarding and within MX6.
Reconciliation Report Summary and Calculation Updates
Updated Valor-based reconciliation summary calculations to apply business rules by transaction type, ensuring only relevant transaction types impact Base, Fee, Total, and the newly added Total Deposits summary row. Sales increase values and refunds decrease them. Backend services and stored procedures were updated to ensure UI totals match Snowflake data based on the selected Deposit Date.
Reconciliation Report Data Field Expansion
Enhanced the Reconciliation Report API to return additional Snowflake transaction fields required for accurate book closing and reporting. The new fields are available in both on-screen API responses and export payloads, with coordinated backend updates to support the additional data elements.
Reconciliation Report Grid and Export Improvements
Improved the Reconciliation Report grid and export to enhance clarity and usability. Updates include new Id and Transaction Type columns, renamed and reordered fields, a Payment Method column displaying card brand and last four digits (or Cash/Check/N/A), updated column labels, inclusion of Deposit Amount and Department fields, consistent negative formatting for refunds, and optimized column layout to prevent horizontal scrolling in both UI and export.
Reconciliation Report UI Improvements
Addressed multiple UI issues in the Reconciliation Report, including date picker navigation alignment, Deposit Date field alignment with design specifications, addition of search and filter capabilities, bold formatting for Summary key values, and ensuring exported reports include column headers even when no data is returned.
MID Formatting Alignment for Production Data
Updated the Report API to trim the first four digits of the MID query parameter before sending Valor queries, aligning with Production DMS data where the MID is stored without leading digits. This resolves data retrieval mismatches in Production while maintaining coordinated non-Production testing adjustments.
Bugs and Fixes
Recurring Billing Infinite Retry Prevention
Fixed an edge case in Recurring Billing decline retry logic that could cause an infinite retry loop when a validation error occurred on invoices no longer eligible for card payments. The system now logs the failure once and suppresses additional retry attempts for 24 hours, preventing repeated error spam and ensuring normal service operation.
Reconciliation Report Access Control Configuration Fix
Resolved a configuration issue that allowed unauthorized merchants in production to access the reconciliation report. Environment-specific settings are now correctly applied during deployment to ensure access is restricted as intended.
Passport Subtotal Validation for Surcharge Transactions
Fixed an issue where Quick Pay transactions with MX Advantage surcharging sent an incorrect subtotal to Passport when the subtotal included the surcharge amount. The payload now correctly separates subtotal and surcharge to prevent validation errors in both UAT and production.
Priority Capital Access Restriction
Restricted Priority Capital access to merchants included in the approved Business ID inclusion list. The left-hand navigation link and related UI access points are hidden for non-approved merchants, direct URL access is blocked with automatic redirection to the Dashboard, and access remains enabled only for specified UAT and QA merchants.
Updated 7 days ago