Release notes v26.06.0
Release Date: June 15, 2026
🚀 What's New?
- New Data Elements for Assisted Card Transaction Risk Management:
Partners on the Shared Authorization model now receive an expanded set of transaction data elements in theOPENLOOP_PRE_AUTHwebhook. These additions deliver richer fraud signals—from digital transaction metadata and shipping details to compromise alerts and on-behalf service results—enabling more precise real-time authorization decisions.- DE 48.06 — Advanced Digital Transaction Data 1 (Phone Number)
- DE 48.08 — Advanced Digital Transaction Data 3 (Shipping Address)
- DE 48.39 — Account Data Compromise Information (ADC Alerts)
- DE 48.71 — On Behalf (OB) Services Results
- DE 23 — Card Sequence Number
- DE 48.32 — Mastercard Assigned ID
- DE 122.1.2 — Acceptor Country Subdivision Code
Reference: Assisted Card Transaction Risk Management (Updated)
Reference: Simulate Card Transactions (Updated)
- SWIFT Payment Rails Coverage Expansion for Cross-Border Payouts: Senders (both business and individual) can now initiate cross-border transfers to recipients in another country using SWIFT payment rails for both local and non-local currencies. This brings SWIFT and LOCAL payment rails together on one platform, significantly broadening payout reach.
- Recipients in a given country can now receive payments in multiple destination currencies—both local and non-local.
- For example, the United Arab Emirates (ARE) supports 27 currencies, including AED, USD, EUR, GBP, HKD, JPY, SGD, AUD, and others.
- Coverage expanded to 200+ countries and 110 unique currencies.
- Partners can now request and receive an MT103 file for every SWIFT transaction to track its status via Freshdesk.
- Enhanced Document API upload logic to support mandatory document upload for specific use cases.
Reach out to your MatchMove implementation manager or the Customer Growth team to learn more.
⚠️ Deprecations & Breaking Changes
- Legacy Staging Base URL Sunsetting —
https://beta-api.mmvpay.com- Applicable: This sunsetting applies to partners who have upgraded to and are currently integrating the v2 Onboarding API.
- Effective: End of June 2026. The legacy unified staging base URL will be permanently decommissioned.
- Starting July 1, 2026: All partners integrating in UAT and staging environments must use the modularized, service-specific base URLs as described in the Begin Technical Integration guide.
- Action required: Migrate all staging and UAT API calls from
https://beta-api.mmvpay.comto the appropriate modularized base URLs before June 30, 2026.
Reference: Begin Technical Integration (Updated)
✨ Enhancements
- Card Order Serviceability API –
line_4 (Region)Requirement Removed (Updated):- The
line_4field is no longer required when checking user address serviceability for card delivery. This simplifies the address validation flow and reduces friction for partners integrating the card order delivery service.
Reference: Check User Address Serviceability (Updated)
⚠️ Important Note
The following changes were applied globally throughout the entire platform. There will be no program configuration upgrade needed for the following:
- New Card Transaction Data Elements and Risk Data
- Partners who are implementing the Shared Authorization model will be able to see the additional data and will be able to use it in their card authorization logic.
- Card Order Serviceability API Update
- Immediately in effect for subscribed partners.
Updates and new capabilities not mentioned above will still require a program configuration upgrade. Our Implementation and Customer Growth teams will evaluate and will reach out to you individually when your program is identified as a candidate for this upgrade.
Need help? Reach out to your MatchMove integration partner or contact the support team.
Interested to learn more?
- Reach out to our Business Development and Customer Growth teams at [sales@matchmove.com].
On this page
- Release notes v26.06.0