# Support
source: https://developer.mastercard.com/account-catalog-services/documentation/support/index.md

## FAQs {#faqs}

The Account Catalog Services API (Customer to Mastercard) enables issuers to efficiently provide Primary Account Number (PAN) data and account-level information through the API and to receive a validation response that contains registration and processed information. For more information, refer to the [Overview](https://developer.mastercard.com/account-catalog-services/documentation/index.md) page. For information about how the Account Catalog Services API works, refer to the [How It Works](https://developer.mastercard.com/account-catalog-services/documentation/index.md#a-account-catalog-services-api) section. All Mastercard customers (such as, Issuers and Processors) to manage their accounts and account relationships for various services provided by Mastercard, can use this API. Mastercard Account Catalog Services for PAN information can be delivered either through the Account Catalog Services API or a Bulk File, or through a user interface upload utility available in Mastercard Connect. The preferred delivery channels are determined by the issuer based on their practices and needs. `RequestID` should be a UUID (Universally Unique Identifier). It will be unique across all the API requests.
In Java, it can be generated using the `randomUUID` method of class java.util.UUID as follows:

* UUID uuid = `UUID.randomUUID()`;
* String requestID = `uuid.toString()`;
1. Questions about API setup, connectivity, or key exchange for Account Catalog Services, contact [API Support](mailto:apisupport@mastercard.com).
2. To find out more about onboarding or any escalation for Account Catalog Services, reach out to your Mastercard representative.
3. For production support, key renewal, or other assistance, contact [Global Customer Support](mailto:customer_support@mastercard.com).
This API provides detailed registration information for the PANs submitted through the Account Catalog Service API.  
For more information, refer to the [Overview](https://developer.mastercard.com/account-catalog-services/documentation/index.md) page. For information about how the Account Catalog Services API works, refer to the [How It Works](https://developer.mastercard.com/account-catalog-services/documentation/index.md#b-account-catalog-services-detail-response-api) section. There are multiple ways of integrating with the Account Catalog Services API:

* Using a Mastercard API Client (recommended)
* Using your own Account Catalog Services API client

For more information about How to Consume the Account Catalog Services API, refer to the [How to Consume the Account Catalog Services API?](https://developer.mastercard.com/account-catalog-services/documentation/api-basics/index.md#how-to-consume-the-account-catalog-services-api)
Refer to the [Tutorials and Guides](https://developer.mastercard.com/account-catalog-services/documentation/tutorials-and-guides/index.md) page for detailed guidance on each of the three phases of integration, such as **Generating a Mastercard API Client** , **Testing the API in the Sandbox (MTF)** , and **Moving to Production**. Account Catalog services uses [JWE Encryption](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/#jwe-encryption) for encrypting and decrypting payload. To avoid service interruptions from expired credentials, project admins will get notifications 90, 60, 30, 15, 7, and 1 day(s) before a credential expires. Upon expiration, project admins will receive an additional email, indicating that the credential is no longer valid. Please go to our main [Support](https://developer.mastercard.com/support) page and click the **Get Help** button to open a support ticket. Our API Support team will assist you in managing your credential to avoid any disruptions to your integration(s).  
For synchronous API calls within Account Catalog Services (ACS), the standard response time SLA is:

* Average response time: 1,000 milliseconds (1 second)
* Maximum allowable response time: up to 3 seconds per request
To add, maintain a key or to upgrade to OAuth 2.0, refer to [OAuth Key Management](https://developer.mastercard.com/platform/documentation/credential-management/oauth-key-management/).

## Help {#help}

### Contact us for technical support. {#contact-us-for-technical-support}