MX Merchant Release Notes

Production Release Date: July 7, 2025

Table of Contents

1. Features
   • International Payments — Corporation Type Mapping for Canadian Merchants
2. Enhancements
   • Support for Secondary Terminal Payments
3. Bugs and Fixes
   • Stripe Payment Intents Not Voided on Terminal Authorization Voids
   • Receipts — Classic Preview and Incorrect Merchant Info in Modern View
   • Contract Payments Missing from History and Completion Status

Features

International Payments — Corporation Type Mapping for Canadian Merchants

This release introduces accurate mapping of Canadian legal entity types in International Payments. Entity jurisdiction kinds in MXConnect are now translated into appropriate CorporationType values in MXM, supporting classifications such as RegisteredCharity, Individual, and Corporation. This replaces the default “Unknown” label and ensures consistency across Checkout API responses, payment broker payloads, and merchant entity records, improving onboarding workflows and regulatory clarity.

Enhancements

Support for Secondary Terminal Payments

Support for secondary terminal transactions has been added by updating the Terminal API and Payment Broker integration logic. The changes include:

• Designating payment.account.network as global to allow optional fields (number, expiry)
• Enabling request_incremental_authorization_support under payment_method_options.card_present for Stripe
• Ensuring secondary actions like SaleCompletion are properly routed and validated

These enhancements streamline terminal payment flows, reduce validation errors, and improve compatibility for multi-step transactions across card-present devices.

Bugs and Fixes

Stripe Payment Intents Not Voided on Terminal Authorization Voids

The Checkout API now correctly cancels associated Stripe payment intents when an authorization is voided at the terminal. This fix prevents payment intents from remaining active in a “waiting to be captured” state, improving alignment between MXM and Stripe and ensuring more accurate transaction reporting.

Receipts — Classic Preview and Incorrect Merchant Info in Modern View

Resolved two receipt-related defects in MXM:

• Classic receipts now load properly without preview errors.
• Modern receipts display the correct business name, email, and address information.

These fixes restore expected receipt behavior during configuration and reduce confusion for merchants reviewing transaction details.

Contract Payments Missing from History and Completion Status

Fixed an issue where one-time contract payments, although successfully processed, did not appear in the payment history or trigger contract completion. The mxg.billing.plan_payment_getpage stored procedure has been updated to retrieve accurate payment data for both Global and standard merchants. This ensures complete visibility in the contract UI and consistent contract status updates.