# Mastercom
source: https://developer.mastercard.com/mastercom/documentation/index.md

## Overview {#overview}

Cardholder disputes usually begin when cardholders or issuers discover possible fraudulent charges or errors on accounts. Issuers and acquirers then attempt to resolve the fraudulent charges or errors by using Mastercom to navigate the dispute resolution cycle.

The dispute resolution cycle includes:

* Collaboration
* First chargebacks
* Second presentments
* Pre-arbitration and arbitration cases
* Pre-compliance and compliance cases
* Fee collections

For more information about the dispute resolution cycle, refer to [Dispute Resolution Cycle](https://developer.mastercard.com/mastercom/documentation/dispute-resolution-cycle/index.md).
Note: For more information about Single Message System dispute processing, see the [Mastercom Extended API](https://developer.mastercard.com/mastercom-extended/documentation/).

## How It Works {#how-it-works}

Mastercom is an end-to-end dispute management system that enables tracking of disputes throughout the entire dispute lifecycle. Dispute events in Mastercom are managed as "claims", regardless of whether they advance to network-level dispute transactions. All activities for any given dispute throughout its lifecycle can be tracked within a single claim.

Issuers can use the Mastercom API to send chargebacks, pre-arbitration and arbitration cases, receive second presentments, and send pre-compliance and compliance cases and fee collections. Acquirers use Mastercom to receive chargebacks, pre-arbitration and arbitration cases, send second presentments and receive and send pre-compliance, compliance and fee collections. The Global Clearing Managements System moves funds from one party to another. Mastercom API facilitates Collaboration with Ethoca and the Merchant.

![how it works](https://static.developer.mastercard.com/content/mastercom/uploads/Mastercom%20API%20Overview%20Graphic%201.jpg)

## Getting Started {#getting-started}

### Before You Start {#before-you-start}

1. Review [client authentication](https://developer.mastercard.com/mastercom/documentation/api-basics/index.md).
2. Integrate with the Mastercom API using one of the [suggested methods](https://developer.mastercard.com/mastercom/documentation/api-basics/index.md#using-a-method-of-your-choice).
3. Review [use cases](https://developer.mastercard.com/mastercom/documentation/use-cases/index.md) to establish the sequence of calls needed to process disputes.
4. Try the [application](https://developer.mastercard.com/mastercom/documentation/developer-tools/reference-app/index.md) in our Sandbox environment and receive mocked responses.
5. Follow the [Quick Start Guide](https://developer.mastercard.com/mastercom/documentation/quick-start-guide/index.md) to begin onboarding.

### Good To Know {#good-to-know}

#### Avoiding Duplicate Dispute Events {#avoiding-duplicate-dispute-events}

Customers are able to send multiple API calls to create dispute events (chargebacks, claims, and so on) within a short time frame. The Mastercom system checks for duplicate dispute events. However, when customers send multiple API calls with duplicate dispute events within a minute, the Mastercom system is unable to check for duplicate dispute events. Therefore, customers should take precautions not to send duplicate dispute events within a minute.

Note: Following the timeout of an API call to create a dispute event, allow more than an hour for a subsequent API call to create the same dispute event.

<br />