MX Merchant Release (September 1, 2025)
MX Merchant Release Notes
Production Release Date: September 1, 2025
Table of Contents
Features
NetSuite Activation Popup
A new confirmation popup has been introduced for MX™ Merchant NetSuite Sync to ensure merchants acknowledge pricing and terms before activation.
Key details:
- Displays once per merchant — immediately post-onboarding if NetSuite is enabled, or on next login if enabled later
- Includes both implementation and monthly fee details, dynamically populated by merchant-level pricing
- Captures merchant response:
- Yes → billing begins immediately
- No → a “NetSuite Declined” case is created automatically
- Prevents repeat display once acknowledged
- Includes full logging for support and audit purposes
This ensures merchants have complete visibility into NetSuite pricing before committing.
Recurring Billing — Reattempting Declined Transactions
MX™ Merchant Recurring Billing now supports automatic reattempts for declined contract payments.
Functionality includes:
- Up to 3 reattempts, once every 24 hours, unless payment succeeds or the contract is paused
- Eligibility follows MerchantAdviceCodeMap rules (excludes declines where RetryPermitted = false)
- Not applicable to the first payment of Bill Now contracts
- All reattempts — successful or failed — are visible in the Payments Grid and Invoice History
This reduces manual merchant intervention and improves collection success rates.
Enhancements
New Column — GlobalPaymentId
A new GlobalPaymentId column has been added to MXG.dbo.Transaction for storing Stripe transaction IDs.
Key updates:
- ReferenceNumber values longer than 12 digits migrated into
GlobalPaymentId - Database, APIs, MX Merchant, and UI components updated for consistent handling
- Ensures cleaner data management and more reliable transaction tracking
Global Terminal Payments — Broker Route Updates
Global terminal payments have been updated so that secondary transactions now use the payment broker backfillable routes (card.reverse, card.complete, card.return, card.void, card.adjust) instead of card.create.
This ensures accurate backfill from the original transaction and aligns all secondary payment operations with expected processing flows.
Checkout API — Sensitive Data Scrubbing
Checkout API logging has been enhanced for PCI-DSS compliance.
Changes include:
- Scrubbing of sensitive customer fields (
name,firstName,lastName) before logs reach Splunk - Prevents potential exposure of Track 1/Track 2 or PAN values when accidentally submitted into customer fields
- Maintains log structure to support troubleshooting and system visibility
Sandbox Performance — Login & Merchant Switching
MX Merchant Sandbox login and merchant-switching performance has been significantly improved.
Improvements include:
- Optimization of the merchant broadcast call
- Archiving of old or deleted broadcasts to reduce processing load
- Faster page load times — resolving delays and blank screens that previously lasted up to 30 seconds
Users will now experience a smoother and more consistent Sandbox workflow.
Bugs and Fixes
Quick Payments — Postal Code & Address Validation
Fixed an issue in Quick Payments where transactions incorrectly failed with a validation message about mismatched postal code and street address.
Fix details:
- Validation logic has been corrected to align with Vortex and Stripe, both of which accept the values without issue
- Updates applied in Checkout API v3
Merchants can now process Quick Payments without false validation errors.
Sandbox — Location Switch & Sign-In Errors
Resolved issues where users were unexpectedly signed out or received 401 Unauthorized errors when logging in or switching locations in Sandbox.
Fix details:
- Prevents unnecessary sign-in cycles when reselecting the same merchant
- Updated Keycloak token lifespans to reduce premature expirations
- Session data now properly managed to avoid authorization mismatches
Merchants can now log in and switch locations reliably in Sandbox.
Updated 23 days ago