# Account Catalog Services
source: https://developer.mastercard.com/account-catalog-services/documentation/index.md

## Overview {#overview}

Account Catalog Services (ACS) API serves as a new channel for submitting Primary Account Number (PAN) data and other attributes for account registration. It is available to issuers and processors for data submission, providing an efficient method for managing accounts and account relationships for various services offered by Mastercard. Users can send a request through the Mastercard gateway to submit information about a new PAN or to provide the latest updated information for an existing PAN.  

Account Catalog Services (ACS) API is available globally across all regions.

Account Catalog Services APIs comprise the following APIs:

### 1. Account Catalog Services API {#1-account-catalog-services-api}

User can submit only one PAN per API request and will receive an immediate acknowledgment indicating whether the request was accepted, rejected, or encountered an error. Issuer can track the status of their request using its unique correlation ID. This applies to any action on Account Identifier such as registration, update, or deletion.   
For more comprehensive information about the various mandatory and optional attributes of this Account Catalog Services API, refer to the [API Reference](https://developer.mastercard.com/account-catalog-services/documentation/api-reference/account-catalog-services-api/index.md) page.
Note: Account Catalog Services uses JWE encryption to provide end-to-end payload encryption to secure sensitive data like Personally Identifying Information (PII). You can download and manage your encryption keys from your [Developer Dashboard](https://developer.mastercard.com/dashboard).

### 2. Account Catalog Services detail response API (Deprecated) {#2-account-catalog-services-detail-response-api-deprecated}

This API functions as an outbound asynchronous push API, transmitting the final processing results to the customer's specified URL through the Account Catalog Services detail response API. For more comprehensive information about the various mandatory and optional attributes of this Account Catalog Services detail response API, refer to the [API Reference](https://developer.mastercard.com/account-catalog-services/documentation/api-reference/account-catalog-services-detail-response-api/index.md) page.

### 3. Account Range Enablement API {#3-account-range-enablement-api}

Account Range Enablement API is used by issuers for submitting Range data and its related other attributes for range registration. For more comprehensive information about the various mandatory and optional attributes of this Account Catalog Services API, refer to the [API Reference](https://developer.mastercard.com/account-catalog-services/documentation/api-reference/account-enablement-api/index.md) page.

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

The following diagram shows a high-level flow between the issuer and Mastercard for the Account Catalog Services submission experience.

### 1. Account Catalog Services API {#1-account-catalog-services-api-1}

![Account Catalog Services Submission Flow](https://static.developer.mastercard.com/content/account-catalog-services/uploads/overviews.png)

1. A user sends a request to Account Catalog Services through the Mastercard API Gateway to add or update accounts.
2. Mastercard API Gateway performs the initial validation. If the validation fails or an error occurs, the user is notified of the error.
3. However, upon successful validation, the Mastercard API Gateway forwards the request to Account Catalog Services.
4. Account Catalog Services processes the request for initial level validations. Once these validations are successful, the request is sent to the respective domain for further processing.
5. The Domain processes the request and performs the necessary business validation for the service in which the PAN is intended to register. It then responds to the Account Catalog Services with the result, indicating either **Accepted** or **Rejected** along with a valid reason.
6. Account Catalog Services receives the response from the respective domain, which will send to the Mastercard API Gateway.
7. Mastercard API Gateway sends a synchronous response to the customer with the registration details for each PAN submitted for processing.

### 2. Account Catalog Services Detail Response API (Deprecated) {#2-account-catalog-services-detail-response-api-deprecated-1}

![Account Catalog Services Response Flow](https://static.developer.mastercard.com/content/account-catalog-services/uploads/outbound-overview.png)

1. The Domain sends the detail response to the Account Catalog Services, if there is any update after the synchronous response.
2. The Account Catalog Services sends the detailed response to the Mastercard API Gateway.
3. The Mastercard API Gateway sends the detailed response to the issuers.
4. The Issuer / Processor sends the acknowledgement of the Account Catalog Services Detail Response API to the Mastercard API Gateway.
5. The Mastercard API Gateway sends the acknowledgement to the Account Catalog Services.

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

To start using the Account Catalog Services API, you must first create a project, and then add the API to it. Contact your Mastercard representative and request your Sandbox (MTF) access.  

Once access is granted, you can use the Sandbox (MTF) environment to test authentication and validate your connectivity. Also, perform end-to-end integration testing based on your integration model in this environment before moving to production. Refer to the [Quick Start Guide](https://developer.mastercard.com/account-catalog-services/documentation/quick-start-guide/index.md) for more information.
Note:   

* Users must provide their email address to provision the service before selecting it from the dropdown menu. Without provisioning, the service will not appear in the dropdown menu.
* To provision your email address, contact the regional CIS team for further processing. This ensures that all required steps are completed and customers receive appropriate support. Users must use the same email address for both Sandbox (MTF) and Production environments to maintain consistency.

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

The various terms associated for the APIs under the Account Catalog Services landscape are:

|                   Terms                    |                                                                                 Description                                                                                 |
|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Account Level Management (ALM)             | Account Level Management is a platform that enables specialized processing so that Mastercard can manage capabilities at the individual card account level.                 |
| Primary Account Number (PAN)               | Primary Account Number allocated to an account by an issuer.                                                                                                                |
| Enhanced Value (ENVL)                      | Enhanced Value provides a reasonable and competitive level of required rewards and enrolls in the reward program, PANs are registered under the approved reward program.    |
| Product Graduation Plus (PGP)              | Product Graduation Plus enables issuers to migrate cardholders across product codes without changing the primary account number (PAN).                                      |
| Consumer Product Monitoring Service (CPMS) | Consumer Product Monitoring Service ensures assignment of the appropriate account category code based on the issued brand product to which the account is being registered. |
| Small Business Spend Processing (SBSP)     | Small Business Spend Processing provides detailed (PAN level) information on the account status qualification for small business.                                           |

## Next Steps {#next-steps}

* For information regarding the different functional flows provided by the application, refer to the [Use Cases](https://developer.mastercard.com/account-catalog-services/documentation/use-cases/index.md) section.
* To understand the request and response formats of the APIs, their models, and examples, refer to the [API Reference](https://developer.mastercard.com/account-catalog-services/documentation/api-reference/index.md) section.
* For any questions about the ID for Trust Providers, refer to the FAQs in the [Support](https://developer.mastercard.com/account-catalog-services/documentation/support/index.md) section.