MX Merchant Release (October 27, 2025)

October 27


MX Merchant Release Notes

Production Release Date: October 27, 2025


Table of Contents

  1. Features
  2. Enhancements
  3. Bugs and Fixes

Features

BIN API Authentication Update

The MXM Bin API now correctly authenticates against the VTX Bin API using the proper eos-tenant-api-token instead of the MXC token. This update resolves previous authentication errors and ensures that valid JWT-based requests return accurate BIN data as expected.


Enhancements

Transaction Report Columns Added

The Transaction report in MX Merchant was enhanced to include new columns for State/Province, Taxes, and Fees. These additions provide users with clearer visibility into regional tax details and associated charges for each transaction.


Network Routing Details in Payments Report

The Payments report now includes network routing details for SMS transactions, showing which debit network (e.g., NYCE, Pulse, STAR) processed each transaction. This enhancement improves transparency for reconciliation, compliance, and operational tracking. The new “Network” column remains blank or marked “N/A” for non-SMS transactions and displays “Unknown” when data is missing.


SMS Transactions Included in Dashboard Volume

The MXM dashboard now includes SMS transactions in total payment volume calculations, ensuring accurate and comprehensive reporting of all processed payments. This update aligns dashboard metrics with backend data and provides a complete view of payment activity across all rails.


Bugs and Fixes

MXM Login and TIN Validation Decoupled from MXC

MX Merchant login has been decoupled from MXC to prevent collateral outages and maintain uninterrupted access when MXC is unavailable. A new getTinInfo parameter in the merchant and checkout API endpoints allows MXM to control when TIN validation occurs—disabled during login for faster access and enabled only when users view the Compliance page.


AutoMapper Mapping Exception Resolved

An issue in the Checkout API that caused mapping errors when retrieving merchant data was fixed by replacing AutoMapper’s cached plan with manual mapping for affected objects. This ensures that requests to retrieve merchant information now return complete data without errors.


AVS Review Indicator Corrected

A defect causing the review flag to appear incorrectly in Checkout API v3 was resolved. The review indicator now only appears when appropriate conditions are met during transaction processing, ensuring accurate fraud and compliance signaling.


Visa DE 25 Mapping Updated for Unattended Terminals

For Visa certification of Unattended Cardholder Activated Terminals, DE 25 value mapping was corrected to set all Visa transactions—both PIN and non-PIN—to “02” when the POS data indicates an unattended device. This change ensures accurate transaction classification and compliance across all checkout systems.


Apple Pay AVS Data Transmission Fixed

The Apple Pay integration was updated to ensure that billing and device information from the wallet is correctly transmitted to the network. AVS (Address Verification Service) data is now properly enriched and included in transactions. Additionally, for cash payments with a provided device ID, the system now retains the given ID instead of defaulting to MXMAPI01, improving transaction and device reporting accuracy.


Back Side


Priority Technology Holdings Logo