Mastercom

Mastercard's end-to-end dispute management system that enables issuers, acquirers, and third parties to manage the full chargeback lifecycle — from pre-chargeback Collaboration through arbitration — through a single consolidated platform.

What it is

Mastercom is Mastercard's formal dispute processing infrastructure. The dispute resolution cycle it handles includes Collaboration (pre-chargeback), first chargebacks, second presentments, pre-arbitration and arbitration cases, pre-compliance and compliance cases, and fee collections. All activities for any given dispute throughout its lifecycle are tracked within a single "claim" in the system (Mastercard Developer Portal, current).

Mastercom sits alongside but is distinct from Mastercard's Global Clearing Management System (GCMS), which handles the actual movement of funds between parties; Mastercom provides the informational and case-management layer on top of GCMS (Mastercard Developer Portal, current).

Where Mastercom fits in the Mastercard ecosystem

The Mastercard dispute ecosystem has three layers, per Rivero (2025-07-18):

Ethoca Alerts — pre-dispute real-time notifications to merchants; if a merchant issues a refund within ~24 hours, the chargeback never reaches Mastercom.
Ethoca Consumer Clarity — recognition-failure reduction at the inquiry stage; surfaces merchant name, logo, and receipts in the issuer's app to resolve "I don't recognise this" disputes before they are filed.
Mastercom — post-dispute formal lifecycle management; invoked when pre-dispute resolution fails.

Ethoca is owned by Mastercard. Consumer Clarity data can be accessed through the Mastercom API — as of July 13, 2026, the GET /v6/claims/{claim-id} response includes a new callCenterDetailsUrl field returning a 15-minute-expiring Consumer Clarity URL, rolling out by region through November 1, 2026, excluding India, Indonesia, Nepal, Jordan, and Tunisia (as-of 2026-07-13) (Mastercard Developer Portal changelog, 2026-07-13).

Collaboration — the mandatory pre-chargeback layer

Collaboration, introduced within Mastercom in September 2022 and made mandatory from early 2023, notifies acquirers of a cardholder dispute before a formal chargeback is filed, placing the chargeback temporarily on hold (Chargebacks911, updated 2025-07-24).

Upon receiving a Collaboration notification, acquirers have 72 hours to respond on the merchant's behalf with one of four outcomes (Justt.ai, updated 2026-07-09):

Accept — Mastercard refunds the issuer directly from the merchant's account
Acknowledge — merchant will issue a direct refund within 72 hours
Disregard — settle bilaterally with the merchant (dispute proceeds to formal chargeback)
Reject — contest the dispute with compelling evidence

Merchant and acquirer participation in Mastercom Collaboration is mandatory, either directly through Mastercom or via an approved third-party facilitator (e.g., Chargebacks911, Justt). Fees are assessed for each notification received; noncompliance fees apply if no response is submitted within the window. Exact fee amounts are not published by Mastercard (Chargebacks911, updated 2025-07-24; Justt.ai, updated 2026-07-09).

Merchants do not access Mastercom directly. For merchants with a direct Ethoca relationship, Collaboration alerts route via Ethoca. Otherwise, notifications route through Mastercom to the acquirer, who then contacts the merchant — making the effective merchant response window dependent entirely on acquirer notification speed (Justt.ai, updated 2026-07-09; ChargebackGurus YouTube, undated).

U.S. healthcare transactions are excluded from automatic Collaboration generation (Mastercard Developer Portal, current).

Unlike Visa's Rapid Dispute Resolution (RDR), Mastercard Collaboration does not use pre-set automatic refund rules; it keeps the response manual and requires the acquirer to act (Justt.ai, updated 2026-07-09).

Technical architecture

Two API variants serve different card system architectures (Mastercard Developer Portal, current):

Mastercom API (Dual Message System) — standard credit and debit cards
Mastercom Extended API (Single Message System) — single-message/debit cards; India customers can process both domestic and cross-border SMS disputes; global customers use only for cross-border SMS

As of October 2024, API versions 2, 3, 4, and 5 were decommissioned; all issuers and acquirers must run on version 6 (as-of 2024-10-01) (Mastercard Developer Portal changelog, 2024-10-01).

Key API changes 2024–2026 (Mastercard Developer Portal changelog):

Oct 2024: acknowledgeFirstPartyTrustEvidence boolean added to POST /v6/claims/{claim-id}/chargebacks; batch acknowledgement limit raised to 500
May 2025: Updated valid fraud type and subtype codes on the fraud reporting endpoint
Aug 2025: auditControNumber field added to GET /v6/claims/{claim-id} — links fraud reporting events to FLD modifications
Apr 2026: Fee endpoints POST /v6/claims/{claim-id}/fees/loaddataforfees and POST /v6/claims/{claim-id}/fee/debitmc deprecated (as-of 2026-04-30)
Apr 2026: Mexico domestic tax/fee fields added to claim and clearing responses
Jul 2026: callCenterDetailsUrl added to GET /v6/claims/{claim-id} — 15-minute Consumer Clarity URL (as-of 2026-07-13)

Duplicate prevention caution: when multiple API calls are made within a minute to create dispute events, the system cannot check for duplicates; callers should wait more than one hour before retrying after a timeout (Mastercard Developer Portal, current).

SAFE — Mastercard's fraud reporting (TC40 equivalent)

SAFE (System to Avoid Fraud Effectively) is Mastercard's process for documenting cardholder fraud claims, directly analogous to TC40 on the Visa network. Issuing banks submit fraud transaction data to Mastercard through SAFE whenever they receive information that a transaction may have been unauthorised (ChargebackGurus, 2025-11-13).

Key distinctions from TC40:

SAFE data is informational only — it does not prevent chargebacks on its own and cannot provide early warning of a pending chargeback (ChargebackGurus, 2025-11-13)
Mastercard gives issuers a generous submission window; SAFE data may reflect fraud activity up to two months old by the time it becomes available (as-of 2025-11-13) (ChargebackGurus, 2025-11-13)

Banks are not required to notify merchants when a transaction is included in a SAFE report; acquirers may share data on request but are not obligated (ChargebackGurus, 2025-11-13)
SAFE feeds into Mastercom's Fraud & Loss Database (FLD); the auditControNumber field in the Mastercom API (added August 2025) provides the linking identifier for FLD events (Mastercard Developer Portal changelog, 2025-08-02)

Practitioners describe an "Ethoca SAFE feed" — a data stream within Ethoca Alerts that specifically conveys issuer-confirmed fraud reports (i.e., SAFE data), distinct from standard consumer dispute alerts. The practitioner view is that SAFE feed inclusion is optional and should be tested based on ticket size and risk profile (Scott Adams, YouTube, undated).

Monitoring programs (ECM, EFM, SMMP)

Mastercard operates monitoring programs that run against network-level data, separate from but related to Mastercom dispute flows (Chargebacks911, 2025):

Program	Trigger	Key threshold (as-of 2025)	Exit condition
ECM — Standard	CNP and CP chargebacks	100+ CB/mo AND ≥1.5% ratio	<100 CB/mo OR <1.5% for 3 consecutive months
ECM — High	CNP and CP chargebacks	300+ CB/mo AND ≥3% ratio	Same pattern at lower threshold
EFM	CNP fraud rate	Single tier; thresholds vary EU vs non-EU	Implement 3-D Secure; meet utilisation threshold
SMMP	Scam / APP fraud	Global CNP programme	New merchant onboarding requirements Jan 2026; enforcement live July 24, 2026 (as-of 2026)

ECM fee range discrepancy: Chargebacks911's FAQ references chargeback fees of $5–$100 per incident; the same site's dedicated ECM programme page references fees of $20–$100. The $5–$100 figure appears in a FAQ context and may conflate scheme fees with processor fees. Source A: Chargebacks911 Collaboration FAQ Source B: Chargebacks911 ECM/EFM programme page

First-Party Trust Program

Mastercard expanded the First-Party Trust Program globally in 2025, giving merchants a mechanism to share enhanced transaction data with issuers; Mastercard's AI validates the evidence and, if successful, grants merchants liability protection (Chargeblast, 2026-03-24).

In the Mastercom API, this is represented by the acknowledgeFirstPartyTrustEvidence boolean field added to POST /v6/claims/{claim-id}/chargebacks in October 2024 (Mastercard Developer Portal changelog, 2024-10-27). This is Mastercard's functional equivalent to Compelling Evidence 3.0 (CE3.0) on the Visa network.

Subscription disputes: Fraud Deflect and Smart Subscriptions (2026)

Mastercard's Fraud Deflect tool integrated with Ethoca Consumer Clarity Smart Subscriptions (announced May 2026), routing cancellation requests from consumers in banking apps directly to subscription merchants — before disputes escalate to Mastercom. As of May 2026, approximately 25% of Mastercard chargebacks are driven by recurring/subscription transactions (as-of 2026-05-04) (Mastercard Newsroom, 2026-05-04).

Scale and performance claims

60% of payment disputes escalate to formal chargebacks (as-of 2026-04-15) (Mastercard Newsroom, 2026-04-15)
Global chargeback volume projected at 324 million by 2028 (as-of 2026-04-15) (Mastercard Newsroom, 2026-04-15)
80% of Fiserv issuer alerts resolved by merchants in under 24 hours via Ethoca integration, preventing the chargeback (as-of 2026-04-15) (Mastercard Newsroom, 2026-04-15)

What practitioners report

Mastercom is not named by practitioners in publicly available YouTube content — the platform operates invisibly to most merchants, who experience only the Collaboration notification and formal chargeback via their acquirer.

Practitioners warn that alert tools (Ethoca, RDR, CDRN) should not be used as a fraud strategy but as a temporary measure while underlying chargeback causes are identified and resolved. Over-reliance on alert suppression prevents merchants from seeing the dispute signals they need to improve (True Fraud Podcast / The Reach Network, undated).

Merchants' effective response window is determined entirely by acquirer notification speed, not by Mastercard's own dispute timelines (ChargebackGurus, YouTube, undated).

Key terms

Term	Meaning
Collaboration	Pre-chargeback 72-hour notification window in Mastercom; mandatory since early 2023
First Chargeback	Formal dispute filed after Collaboration window; reverses funds
Second Presentment	Merchant counter to a first chargeback
SAFE	System to Avoid Fraud Effectively — Mastercard's TC40-equivalent fraud reporting
ECM	Excessive Chargeback Merchant monitoring programme
EFM	Excessive Fraud Merchant monitoring programme
SMMP	Scam Merchant Monitoring Programme — enforcement live July 24, 2026
FLD	Fraud & Loss Database — where SAFE/fraud data is recorded
DMS	Dual Message System — standard credit/debit; uses Mastercom API
SMS	Single Message System — debit; uses Mastercom Extended API
GCMS	Global Clearing Management System — the fund-movement layer beneath Mastercom

Benchmarks (as-of 2026)

Metric	Value	Source	As-of
% disputes escalating to chargebacks	60%	Mastercard Newsroom / Fiserv	2026-04-15
% chargebacks from subscriptions/recurring	~25%	Mastercard Newsroom	2026-05-04
% Fiserv alerts resolved <24h	80%	Mastercard Newsroom	2026-04-15
Global chargebacks projected by 2028	324 million	Mastercard Newsroom	2026-04-15
ECM standard threshold	100 CB/mo + ≥1.5% ratio	Chargebacks911	2025
ECM high tier threshold	300 CB/mo + ≥3% ratio	Chargebacks911	2025
Mastercom cost reduction claim	20%	Mastercard (via Justt.ai)	undated — unverified

Frontier links

Mastercard First-Party Trust · GMAP · SMMP (Scam Merchant Monitoring Program) · ECM (Excessive Chargeback Merchant) · EFM (Excessive Fraud Merchant) · Fraud Deflect · SAFE (Mastercard) · Mastercard Chargeback Monitoring Program (MCMP) · Mastercard Transaction Level Identifier Data