Solidgate logo in black and white.

Mastercom collaboration

What is Mastercom Collaboration?

Mastercom Collaboration is a pre-chargeback workflow inside , Mastercard's dispute management platform, that alerts a as soon as a disputes a transaction and before that dispute becomes a . It gives merchants near real-time visibility into dispute activity on their Mastercard volume.
The alert travels from the through the Mastercard network to the , which relays it to the merchant. Mastercom is the end-to-end system Mastercard uses across the dispute lifecycle; Collaboration is the module that opens a window before the chargeback is filed. Coverage is limited to Mastercard-branded transactions, so disputes raised on other travel through their own prevention channels.

Key facts

  • Sits inside: Mastercom, Mastercard's dispute management platform
  • Scope: Mastercard-branded transactions only
  • Response window: 72 hours from the alert for the merchant to act
  • Participants: cardholder, issuer, acquirer, merchant
  • Merchant options: and close the case, or decline and defend the chargeback if the cardholder proceeds
  • No automatic refund: unlike Visa's , Collaboration alerts don't issue a refund on their own

How it works

  1. The cardholder files a dispute. The cardholder contacts their issuer about a Mastercard transaction they don't recognize or want reversed.
  2. The issuer raises the case in Mastercom. The dispute enters the Mastercard network before any chargeback is filed against the merchant.
  3. Mastercard sends a pre-chargeback alert. The alert goes to the acquirer and carries the transaction details and the .
  4. The acquirer relays the alert to the merchant. Acquirers and payment processors pass alerts through a dispute feed or API so they reach the merchant's operations queue automatically.
  5. The merchant responds within 72 hours. A refund issued inside the window closes the case and no chargeback follows. If the merchant declines or lets the window expire, the issuer proceeds to file the chargeback and the case moves into the standard flow.

Why it matters

  • A refund issued inside the window closes the case before a chargeback exists, so the transaction never counts toward the ratio measured by the .
  • Alerts arrive with the dispute reason attached, which separates genuine card fraud from on the same order.
  • Merchants shipping physical goods can halt fulfillment on a flagged order, which is why just-in-time shipping decisions are a common use of the alert feed: the merchant avoids losing both the goods and the payment.
  • Each dispute closed pre-chargeback removes the chargeback fee the acquirer would otherwise pass on for that case.

Common issues

  • The 72-hour window is short. Manual review of every alert stops scaling past low dispute volumes, and unreviewed alerts become chargebacks by default.
  • Refunding every alert is expensive. A blanket refund policy gives up revenue on disputes the merchant could have won with evidence, including friendly fraud cases.
  • Coverage is Mastercard-only. Visa and American Express disputes need separate prevention channels, so a merchant relying on Collaboration alone sees only part of its dispute volume early.
  • Alerts aren't case files. The notification carries the dispute reason, not the issuer's full evidence requirements, so the refund-or-fight decision is made on partial information.

Related terms