# Support source: https://developer.mastercard.com/mastercom-extended/documentation/support/index.md ## FAQ {#faq} ### General {#general} The [Mastercom API](https://developer.mastercard.com/mastercom/documentation/) consists of endpoints used by issuers and acquirers to manage disputes for cleared Dual Message System original transactions. The [Mastercom Extended API](https://developer.mastercard.com/mastercom-extended/documentation/) consists of endpoints used by issuers and acquirers to manage disputes for cleared Single Message System original transactions. In the future, Mastercard will enhance the Mastercom Extended API with new endpoints to include additional functionality. The Mastercom Extended API will eventually replace the Mastercom API. The Mastercom API is referred to as Mastercom V6 throughout this documentation site. Customers in India can manage their domestic (Single and Dual Message) transaction disputes and cross-border (Single Message) transaction disputes using the Mastercom Extended API. Customers in India with domestic transaction disputes must use the India domain names to submit their API calls. Global customers will continue to use Mastercom Extended API to manage Single Message transaction disputes. | Customer | Single Message | Dual Message | |--------------------|-------------------------------------------------------|-------------------------------------------------------------------------------| | India domestic | | | | India cross-border | | [Mastercom V6 API](https://developer.mastercard.com/mastercom/documentation/) | | Global | | [Mastercom V6 API](https://developer.mastercard.com/mastercom/documentation/) | For further information, refer to [AP 12116.1 Mastercom Extended for Issuers and Acquirers in India](https://trc-techresource.mastercard.com/r/bundle/m_an12116_en-us/page/d/en-US/) in the Technical Resource Center on Mastercard Connect. Refer to the Technical Resource Center on Mastercard Connect for production dates by region. > * [US 8733.6 Migration of Single Message System Dispute Processing into Mastercom](https://trc-techresource.mastercard.com/r/bundle/m_AN8733_en-us/page/d/en-US/) > * [LAC 10231.3 Migration of Single Message System Dispute Processing into Mastercom](https://trc-techresource.mastercard.com/r/bundle/m_an10231_en-us/page/d/en-US/) > * [MEA 10740.3 Migration of Single Message System Dispute Processing into Mastercom](https://trc-techresource.mastercard.com/r/bundle/m_an10740_en-us/page/d/en-US/) > * [AP 11197.3 Migration of Single Message System Dispute Processing into Mastercom for the Asia/Pacific Region (excluding India and Indonesia)](https://trc-techresource.mastercard.com/r/bundle/m_an11197_en-us/page/d/en-US/) > * [CAN 10801.3 Migration of Single Message System Dispute Processing into Mastercom for the Canada Region](https://trc-techresource.mastercard.com/r/bundle/m_an10801_en-us/page/d/en-US) Settlement occurs when a switch completes processing of the dispute event. The dispute resolution cycle includes: > * First chargebacks > * Representments > * Pre-arbitration and arbitration cases > * Pre-compliance and compliance cases > For more information about the dispute resolution cycle, see [Dispute Resolution Cycle](https://developer.mastercard.com/mastercom/documentation/getting-started/#dispute-resolution-cycle). ### Onboarding {#onboarding} 1. Review [API Basics](https://developer.mastercard.com/mastercom-extended/documentation/api-basics/index.md). 2. Integrate with the Mastercom Extended API using one of the [suggested methods](https://developer.mastercard.com/mastercom-extended/documentation/api-basics/index.md#use-a-method-of-your-choice). 3. Review [use cases](https://developer.mastercard.com/mastercom-extended/documentation/use_cases/index.md) to establish the sequence of calls needed to process disputes. 4. Try the [reference app](https://developer.mastercard.com/mastercom-extended/documentation/developer-tools/reference-app/index.md) in the Sandbox environment and receive mocked responses. 5. Follow the [Quick Start Guide](https://developer.mastercard.com/mastercom-extended/documentation/quick-start-guide/index.md) to begin onboarding. Mastercard recommends using a different client key for Mastercom Extended. Review [Credential Management](https://developer.mastercard.com/platform/documentation/credential-management/). API keys expire every 13 months. Customers are responsible for tracking expiration to prevent unexpected API failures. The key owner or an administrator may grant access to additional users under the same key. 1. Track key expiration to maintain visibility into the lifecycle of all API keys used in your project. 2. Subscribe to key life cycle notifications by enabling notifications, including expiration alerts, and monitor them regularly. 3. Add multiple subscribers to ensure multiple users (such as key owners, administrators, and backup contacts) receive lifecycle notifications. 4. Plan key rotation in advance to generate and transition to a new key before the current key expires. Key owners and project administrators receive multiple notifications prior to expiration and an additional notification once the key has expired. Refer to [Credential Management](https://developer.mastercard.com/platform/documentation/credential-management/) for additional information. ### Policy {#policy} Yes, all of our APIs are PCI compliant. The throttling policy is as follows: 150 requests per second. ### Performance {#performance} The timeout for Mastercom Extended is set to 15 seconds. ### Support {#support} 1. Follow the [Quick Start Guide](https://developer.mastercard.com/mastercom-extended/documentation/quick-start-guide/index.md) to request access to this service. 2. Connect with a Regional Representative:After your request is submitted, a regional Mastercard representative provides further information about the Mastercom Extended program and guides you through the registration and eligibility requirements. 3. Begin Implementation: When you are ready for program implementation, you are assigned a Mastercard Delivery Manager who will guide you through integration. ## Get Help {#get-help} ### Contact us for technical support {#contact-us-for-technical-support}