📚 2026 Release Notes
MAY 10, 2026
| WHAT'S NEW | Checkout API v3 now supports an optional employee field on payment creation and retrieval, enabling attribution of transactions to specific staff members for reporting and reconciliation. The field is validated as a string with a maximum of 16 characters, persisted with the payment record, and returned in GET responses without impacting existing integrations. |
| ENHANCEMENT | Improved WebSocket performance and stability for Vortex payment integration by introducing a redesigned connection pool with dynamic scaling, idle eviction, and enhanced retry logic with exponential backoff and timeout handling. Refactored client logic for better maintainability, increased test coverage, and ensured timed-out transactions trigger automatic reversals, with post-deployment monitoring in place to validate behavior under production load. |
| BUG FIX | Resolved an issue where newly uploaded ePay logos were not appearing on the ePay domain despite successful upload, caused by inconsistencies in image storage and retrieval. Logo uploads are now properly persisted and served via the configured S3 storage solution, ensuring branding displays correctly across environments. |
| BUG FIX | Fixed an issue where recurring contracts set to Send Invoice displayed an incorrect Last Billed Date, causing inconsistencies with actual payment records and billing history. The system now updates the Last Billed Date based on the most recent successful payment, ensuring alignment with invoice data and preventing confusion when switching billing methods. |
Read more about this release →
APRIL 26, 2026
| ENHANCEMENT | Expanded refund volume limit enforcement to include TSYS and Fiserv merchants with SMS PIN Debit enabled by evaluating only SMS PIN Debit refund volume against the configured threshold. Once the limit is reached or exceeded, subsequent refund transactions are declined using existing behavior while maintaining current functionality for Priority Global merchants. |
| ENHANCEMENT | Refactored the customer export query to remove its dependency on the full-text index and replace it with standard SQL query logic while maintaining functionality and performance. Export results remain accurate and consistent with validation confirming behavior matches previous output. |
| ENHANCEMENT | Refactored the product search query to remove its dependency on the full-text index and replace it with standard SQL query logic while preserving functionality and maintaining comparable performance. Search results remain accurate and consistent following validation. |
| ENHANCEMENT | Refactored the supplier search query to remove its dependency on the full-text index and replace it with standard SQL query logic while preserving functionality and maintaining comparable performance. Search results remain accurate and consistent following validation. |
| BUG FIX | Fixed an issue on the Funding (EFT) transaction detail page where the React loader caused transaction data to fail loading correctly after a page refresh. Transaction details now display consistently without missing or corrupted data after reload. |
| BUG FIX | Fixed an issue where refunds failed with an Invalid fee amount error if MX Advantage was disabled after processing a payment. Refunds for previously processed transactions now succeed regardless of the current MX Advantage state. |
| BUG FIX | Resolved an issue where invoice emails failed to send after manual status changes due to improper handling of quoted strings in invoice history descriptions. Updated database logic and string handling across SQL, API, and email templates to ensure consistent escaping, prevent deserialization errors, and restore successful email delivery. |
Read more about this release →
APRIL 12, 2026
| WHAT'S NEW | Enhanced payment notifications to include detailed invoice information, providing recipients with clearer context about their transactions directly within email communications. |
| ENHANCEMENT | Updated the Fiserv Omaha TapTrans settlement file format for MasterCard by expanding the Unit Measure Code field and adjusting subsequent field positions to align with TapTrans 038 specifications, ensuring successful validation without impacting non-MasterCard processing. |
| ENHANCEMENT | Refactored the card vaulting flow to use a reliable merchant identifier instead of customer-based mapping, resolving issues caused by customers associated with multiple merchants and restoring stable Stripe vaulting functionality for both global and non-global merchants. |
| ENHANCEMENT | Updated invoice SMS messaging to remove MX Merchant branding and ensure communications appear merchant-branded, while preserving functionality such as access codes, opt-out instructions, and dynamic links, providing a more consistent and clear customer experience. |
| ENHANCEMENT | Enhanced the MX Merchant Valor reconciliation report to separately summarize SMS PIN Debit and credit card deposits for eligible merchants by introducing Debit Deposits and Credit Deposits line items, driven by merchant entitlement and updated query logic, while preserving the existing single total for merchants without PIN debit enabled. |
| BUG FIX | Fixed an issue where MXM payment filters were not functioning correctly by addressing underlying data and default value handling, ensuring accurate filtering of payment records in the UI. |
| BUG FIX | Fixed an issue where declined refunds from Vortex were incorrectly marked as successful by removing override logic for Vortex-processed transactions, ensuring refund statuses accurately reflect network responses while preserving existing behavior for legacy payment flows. |
| BUG FIX | Fixed an issue where invoice and recurring refunds could fail after a rapid refund due to incorrect paid amount calculations by updating the validation logic to include only approved transactions, ensuring refunds process correctly once the merchant account is unlocked. |
| BUG FIX | Fixed an issue where processorName and processorPlatform were not correctly set to Priority for downline partners, ensuring accurate population of merchant.account and merchant.processor records during boarding across multi-level partner hierarchies. |
Read more about this release →
MARCH 29, 2026
| ENHANCEMENT | Updated invoice SMS messaging to remove platform branding, ensuring messages are fully merchant-branded while preserving functionality such as invoice access links, verification codes, and STOP/HELP compliance text. |
Read more about this release →
MARCH 15, 2026
| WHAT'S NEW | Merchants can now enable custom invoice numbers in Invoice Settings. When enabled, invoice creators can enter an alphanumeric invoice number of up to 8 characters during invoice creation. If no value is provided, the system continues to generate invoice numbers automatically. |
| WHAT'S NEW | The Portal Information section now dynamically displays the appropriate tax identifier label based on the identifier used during merchant boarding, including SSN, ITIN, or EIN. If the system cannot determine the specific identifier type, a generic Tax Identifier label is displayed while maintaining existing masking behavior. |
| ENHANCEMENT | Vaulted card handling has been enhanced for Priority International merchants using Stripe. When a card is vaulted, the system now creates a corresponding Stripe customer and card record, requiring the customer to have at least one email address. Each vaulted card generates additional vault records to support Stripe card-on-file processing. |
| ENHANCEMENT | Payments made with vaulted cards for Priority International merchants now use Stripe tokens for processing from both the UI and Checkout API. Recurring contract payments use the off-session version of the vaulted card, and surcharges are ignored because Stripe does not support surcharges for recurring payments. Vaulting cards during terminal payments has also been disabled for these merchants to ensure Stripe compatibility. |
| ENHANCEMENT | A new ACH Funding Report has been added for Puerto Rico merchants, based on the existing Priority International Canada report structure. The Transactions report has also been updated to rename the Province column to Territory to better reflect regional terminology. |
| ENHANCEMENT | Transaction query performance has been improved by limiting a key stored procedure to a rolling two-year transaction date window, reducing the amount of historical data scanned and improving execution performance as the Transactions table grows. |
| BUG FIX | Stored procedures associated with the Transaction Batch table were refactored to remove dependency on a full-text index previously used for search functionality. Queries now use standard SQL filtering logic while maintaining consistent results in the Batches view. |
Read more about this release →
MARCH 1, 2026
| WHAT'S NEW | SMS Batch Report and SMS Transactions Report are now available in MXM, providing clients visibility into SMS batches and transactions processed by Priority that are not reported via TSYS or First Data. Report data aligns with MXC records to ensure accuracy and consistency, access is restricted to authorized clients only, and batches with a status of funded are correctly included in report queries to support contractual reporting requirements and full transaction transparency. |
| ENHANCEMENT | Enhanced the merchant boarding process to support merchant-level currency configuration by introducing a Merchant_Currency relationship that stores supported currencies received during onboarding and associates them with each merchant account. |
| ENHANCEMENT | Updated the Checkout API and MX Merchant Terminal API to use the currency configured during merchant boarding instead of defaulting based solely on country, ensuring transactions are processed using explicitly assigned supported currencies and improving alignment between onboarding configuration and live payment processing. |
Read more about this release →
FEBRUARY 15, 2026
| WHAT'S NEW | MXM now supports multiple Stripe platform accounts, enabling transaction processing across Priority Commerce Canada, Priority Technology Holdings, and future regional platforms while enforcing immutability of the merchant country after boarding. |
| WHAT'S NEW | SMS Batch Report is now available in MXM, providing visibility into SMS batches processed by Priority that are not reported via TSYS or First Data, with data aligned to MXC and access restricted to authorized clients. |
| WHAT'S NEW | SMS Transactions Report is now available in MXM, delivering full visibility into SMS transactions processed by Priority that are not reported via TSYS or First Data, with data consistency aligned to MXC and access limited to authorized clients. |
| WHAT'S NEW | Implemented JWT support in MXM Checkout, validating Keycloak tokens against the configured JWKS endpoint and securely exchanging them for internal AccessTokens while maintaining compatibility with legacy authentication methods. |
| WHAT'S NEW | Enterprise merchant approvals now automatically create or link a partner user when the MXM product is approved, ensuring proper user association when at least one feature is enabled. |
| ENHANCEMENT | Re-enabled cash and check payment methods for eligible Canadian merchants, restoring non-card payment acceptance during onboarding and within MX6. |
| ENHANCEMENT | Updated reconciliation summary calculations to apply transaction-type business rules, added a Total Deposits row, and ensured UI totals align with Snowflake data based on Deposit Date. |
| ENHANCEMENT | Expanded the Reconciliation Report API to include additional Snowflake transaction fields in both on-screen views and export payloads to support accurate book closing and reporting. |
| ENHANCEMENT | Improved the Reconciliation Report grid and export with new and renamed columns, clearer payment method formatting, negative refund formatting, inclusion of Deposit Amount and Department fields, and optimized layout without horizontal scrolling. |
| ENHANCEMENT | Addressed multiple Reconciliation Report UI gaps including date picker alignment, Deposit Date field updates, search and filter capabilities, bolded summary values, and consistent export headers even when no data is returned. |
| ENHANCEMENT | Updated MID formatting logic to trim leading digits before Valor queries, aligning with Production DMS data storage and resolving data retrieval mismatches. |
| ENHANCEMENT | Restricted Priority Capital access to approved merchants only by hiding navigation links, blocking direct URL access, and redirecting unauthorized users to the Dashboard. |
| BUG FIX | Resolved an edge case in Recurring Billing decline retry logic that could cause an infinite retry loop by logging the failure once and suppressing additional retries for 24 hours. |
| BUG FIX | Fixed a production configuration issue that allowed unauthorized merchants to access the Reconciliation Report by ensuring environment-specific settings are correctly applied during deployment. |
| BUG FIX | Corrected Quick Pay surcharge payload handling so subtotal and surcharge amounts are properly separated, preventing Passport validation errors in UAT and production. |
Read more about this release →
FEBRUARY 1, 2026
| WHAT'S NEW | The Terminal API now supports multiple Stripe platform accounts, enabling transaction processing across Priority Commerce Canada, Priority Technology Holdings, and future regional accounts while maintaining full compatibility with existing terminal operations. |
| ENHANCEMENT | Payment Links have been optimized for mobile devices to provide a more polished and consistent experience, with improved layout behavior and reduced unnecessary white space on phones and tablets. |
| BUG FIX | The Auth Settlement Difference risk check has been corrected to properly detect significant discrepancies between authorization and settlement amounts, ensuring the risk flag triggers correctly and surfaces affected merchant accounts for review. |
Read more about this release →
JANUARY 18, 2026
| WHAT'S NEW | Terminal payments now dynamically determine transaction currency based on the merchant’s country, with country code metadata included in requests to Stripe to ensure accurate international payment processing. |
| ENHANCEMENT | Updated the MXM Web application to a newer Node.js runtime targeting Node 20.x to improve platform supportability and alignment with current standards, while maintaining full compatibility across all environments. |
| ENHANCEMENT | Improved currency handling within Checkout by defaulting to USD when a currency code is not provided and introducing consistent currency and country code mappings for downstream processing. |
| ENHANCEMENT | Enhanced VTX and MX Merchant Payments reports by displaying network names for SMS transactions, defaulting to Debit when unavailable, and updating the Card Sub Type column to reflect card level values for both SMS and DM transactions. |
| BUG FIX | Stabilized the Checkout API to prevent server crashes during payment validation failures, ensuring invalid payment attempts return a proper 400 validation response instead of triggering HTTP 5XX errors. |
Read more about this release →
Updated 13 days ago