Mastercard Acquirer Collaboration Ends in January 2027

What Mastercard is removing from Mastercom

This announcement is filed under Pricing/Fees with a Financial action indicator, which is part of why it is easy to miss in a queue of routine pricing updates. What it announces is a service decommission.

Mastercard states that it will decommission the Mastercom Acquirer Collaboration service in the US and Canada regions. At the time of decommission, notifications for the service are turned off and the associated billing codes are set to USD 0. Customers currently using Acquirer Collaboration lose access to the service, including notifications and dispute acquirer collaboration functionality, following the effective date.

The four billing events being zeroed out, all under Service ID MW:

• 2MS4000, Collaboration Funds Movement Fee
• 2MS4001, Collaboration Non-Compliance Fee
• 2MS40021, Collaboration Resolution/Response Fee (Tier 1), covering any card acceptor business code not included in Tier 2
• 2MS40022, Collaboration Resolution/Response Fee (Tier 2), covering selected MCCs

Mastercard’s stated rationale is long-term platform simplification and improved customer experience. The background section adds that as the network modernizes its dispute solutions, including the introduction of new platforms, existing collaboration capabilities will be replaced with more advanced, streamlined processes. The bulletin references AN 4387 and AN 4655 for prior context on acquirer inclusion in the Mastercom Collaboration process.

Two dates govern your planning. July 21, 2026 closed the door on new enrollment. January 4, 2027 ends the service for everyone still on it.

Both dates are region-specific. CAN/US 14059.1 is filed as a US and Canada announcement, and Mastercard has not published a comparable timeline for Europe, Asia/Pacific, Latin America and the Caribbean, or Middle East and Africa. Acquirer inclusion in the Collaboration process was established across regions under AN 4655, so companion announcements elsewhere would be a reasonable expectation, though the network has committed to nothing publicly. If your portfolio extends beyond North America, confirm regional scope with your Mastercard representative before applying the January 4 date globally. We are watching for follow-up announcements and will update this piece as dates are published.

Where Acquirer Collaboration sits in the current flow

You know the architecture, but the specific dependency is worth restating because it determines who in your portfolio is exposed.

Mastercom Collaboration allows communication between issuers, acquirers, and merchants to resolve disputes prior to chargeback initiation. Within that feature, routing splits on one condition: whether the merchant descriptor is registered through Ethoca.

Registered descriptors take the direct path. Issuer to Ethoca to merchant, on Ethoca rails, with your platform or the merchant’s provider handling response. Unregistered descriptors take the acquirer path. Issuer to Mastercom, then along Ethoca rails to the acquirer, at which point distribution to the merchant becomes your responsibility. AN 4655 formalized acquirer inclusion in that process. Acquirer Collaboration is the mechanism supporting transactions outside the Ethoca network, and Mastercard’s bulletin describes it in exactly those terms.

The practical consequence is that Acquirer Collaboration has functioned as portfolio-wide backstop coverage. Every Mastercard dispute generated a notice regardless of whether the individual merchant had done anything to enroll. After January 4, 2027, in the US and Canada, that backstop is gone and coverage becomes a function of descriptor registration alone.

What the decommission removes from your operation

The impact splits across three areas, and they do not land on the same teams.

Notification coverage for unregistered descriptors

Any merchant in your book whose descriptors are not registered through Ethoca currently receives Mastercard pre-chargeback notices only because you receive them first. Once notifications are switched off, those disputes could potentially proceed directly to chargeback with no intervening window. The volume affected depends entirely on your registration rate, which is measurable today and worth measuring now rather than in Q4.

The fee structure and the compliance line

Zeroing the Resolution/Response tiers removes a cost line, and for MSPs that absorbed rather than passed through the Mastercom route pricing, that is a real reduction. The Non-Compliance Fee going to USD 0 is more interesting. That fee was the enforcement mechanism attached to Collaboration response obligations. Its removal in these regions raises a question the bulletin does not answer, which we get to below.

Integration and case-routing logic

If your platform consumes Mastercom Collaboration API calls for acquirer-routed cases, builds merchant-facing notifications from them, or runs SLA timers against the response window, that code path has a termination date. Sunsetting it cleanly means identifying every downstream dependency: merchant portal notifications, internal case queues, reporting that counts Collaboration-routed resolutions as prevented chargebacks, and any contractual language with merchants that references the coverage.

Quantifying portfolio exposure before January

The analysis is straightforward and the output is a number you can act on.

Start with descriptor-level registration status across your entire merchant base. Segment by Mastercard volume, then by current dispute rate. Merchants with high Mastercard volume and no Ethoca registration are the concentrated risk, and there are usually fewer of them than expected, which makes remediation tractable.

Layer in your Mastercard dispute counts routed through Acquirer Collaboration over the last twelve months. That figure represents the notices that will simply stop arriving. Some portion of those were resolved before chargeback initiation. That resolved portion is your projected chargeback increase if nothing changes, and it feeds directly into merchant-level counts that Mastercard’s monitoring categories track.

For merchants sitting near program thresholds, even a modest shift in chargeback counts could potentially move them across a line. The count-based construction of Mastercard’s monitoring categories means the effect shows up regardless of ticket size, which is why low-average-ticket merchants in your portfolio deserve a closer look than their revenue contribution might suggest.

Open questions the announcement leaves unresolved

Mastercard has published the end date without publishing the replacement. Several things remain unstated.

The announcement references the introduction of new platforms and more advanced, streamlined processes, but names no platform, describes no functionality, and gives no availability date. There is no stated migration path for existing integrations. AN 4655 established acquirer inclusion in the Collaboration process as an obligation, and the decommission announcement does not address how that obligation is affected once the mechanism supporting non-Ethoca transactions is retired. The scope is limited to the US and Canada regions, with no comment on other regions. And nothing addresses whether merchants relying solely on the acquirer route receive any transitional coverage.

We are treating the direct Ethoca path as the operating assumption until Mastercard says otherwise, and monitoring for follow-up bulletins. Anyone building a 2027 roadmap on the premise that a drop-in replacement will arrive in time is taking a position the published record does not currently support.

Rebuilding coverage on the remaining path

The remediation work is enrollment work, and it scales with portfolio size rather than complexity.

Descriptor registration through Ethoca is the primary lever. Alerts route directly to the enrolled merchant or their designated provider, which removes your distribution burden entirely and typically delivers faster than the multi-hop acquirer route ever did. For MSPs, the enrollment campaign itself is a defensible touchpoint with merchants and a reason to open a wider conversation about dispute coverage.

Coverage on the Visa side should be reviewed in the same pass. Verifi CDRN operates a refund-before-chargeback model on Visa transactions, and Visa RDR automates resolution against merchant-defined rules. Portfolios that built Mastercard coverage around Acquirer Collaboration frequently have proportionate gaps on Visa that nobody has audited recently.

Consolidation matters more than any single connection. Managing Ethoca Alerts, Verifi CDRN, and Visa RDR through separate integrations means a network-side change on any one of them produces exactly the situation this bulletin created: a coverage gap that surfaces months later in chargeback reporting rather than immediately in an operations dashboard.

Map your exposure before the January deadline

If you need to quantify Acquirer Collaboration exposure across your portfolio and close the registration gaps before January 4, 2027, there is time to do it properly if you start this quarter. Our team can run descriptor-level coverage analysis across your merchant base, identify the accounts carrying the most risk from the notification loss, and handle enrollment and integration so your merchants stay covered through the transition. Contact us to scope the analysis against your current book.

Why ChargebackHelp?

Network program changes are constant, and each one shifts operational burden onto the acquirers and ISOs sitting between the network and the merchant. ChargebackHelp is built to absorb that. Our RESOLVE solution consolidates Ethoca Alerts, Verifi CDRN, Visa RDR, and dispute notices into a single portfolio-wide interface, so a decommission on one rail does not create a silent gap across thousands of merchant accounts. DEFLECT mobilizes transaction and fulfillment data to cardholders and issuers at the point of inquiry, reducing dispute volume upstream of any alert. RECOVER automates representment on chargebacks worth contesting. For MSPs, that combination doubles as a differentiator you can put in front of merchants, and as one fewer network deadline your team has to project-manage alone.