# Designing your CMP account

### Understanding Accounts <a href="#understanding-accounts" id="understanding-accounts"></a>

Accounts in the Card Management Platform serve as distinct, logical units for managing card services and credentials. Think of them as containers that isolate and organize your card-related activities.

#### Purpose <a href="#purpose" id="purpose"></a>

Accounts enable you to segment and manage different sets of cards and services. They also allow for separate enrollments with third parties such as VISA, Mastercard, American Express, and Discover in the situation that the third party requires separate enrollments into services per-merchant.

For merchant aggregators such as Payment Service Providers (PSPs), PayFacs, and Marketplaces, this allows for clear separation of merchant data, where each merchant can have its own dedicated account.

#### Key Characteristics <a href="#key-characteristics" id="key-characteristics"></a>

* Each account is uniquely identified by a Tenant ID (also referred to as a *Vault ID* or *Account ID*).
* Cards created within an account are exclusive to that account.
* Service configurations and settings are applied at the account level.

### Account Configuration Options <a href="#account-configuration-options" id="account-configuration-options"></a>

The platform offers flexible service configuration options at both the account and network levels:

#### Account-Level Service Control <a href="#account-level-service-control" id="account-level-service-control"></a>

* You have the ability to enable or disable services for the entire account.
* This provides a global setting for all cards within the account.

| Service                                                                                                              | Overall Service Configuration                                                     |
| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| [Account Updater](https://docs.verygoodsecurity.com/cmp/products-and-services/account-updater)                       | Enabled/Disabled                                                                  |
| [Network Tokens](https://docs.verygoodsecurity.com/cmp/products-and-services/network-tokens)                         | Enabled/Disabled                                                                  |
| [Card Art](https://docs.verygoodsecurity.com/cmp/products-and-services/card-art)                                     | Enabled/Disabled                                                                  |
| [Duplicate Card Check](https://docs.verygoodsecurity.com/cmp/payment-credentials/cards#duplicate-card-detection)     | Enabled/Disabled                                                                  |
| [Card Attributes (Enriched Attributes)](https://docs.verygoodsecurity.com/cmp/products-and-services/card-attributes) | Disabled by default. For upgrade, please contact support via **<support@vgs.io>** |
| [3DS](https://docs.verygoodsecurity.com/cmp/products-and-services/3ds)                                               | Enabled/Disabled                                                                  |

#### Network-Level Service Control <a href="#network-level-service-control" id="network-level-service-control"></a>

You can further refine service settings by enabling or disabling services at the network level (e.g., Visa, Mastercard). This allows for granular control over service availability based on the card network. Both **Account Updater** and **Network Token** services can be individually enabled or disabled per network, based on your business requirements.

| Service                                                                                        | Network-Level Configuration |
| ---------------------------------------------------------------------------------------------- | --------------------------- |
| [Account Updater](https://docs.verygoodsecurity.com/cmp/products-and-services/account-updater) | Enabled/Disabled            |
| [Network Tokens](https://docs.verygoodsecurity.com/cmp/products-and-services/network-tokens)   | Enabled/Disabled            |

#### Enrollment Types <a href="#enrollment-types" id="enrollment-types"></a>

The platform supports two enrollment types, determining how services are activated:

#### **On-Create Enrollment**

* This is the default setting.
* When a card object is created, the system automatically processes and activates the services enabled for the account.
* A webhook notification is sent upon successful service activation.

#### **Manual Enrollment**

* With manual enrollment, card creation does *not* automatically trigger service activation.
* You must explicitly invoke individual service endpoints to perform actions like network tokenization or account updater participation.
* This provides greater control over the timing of service activation.

| Service                                                                                        | Enrollment Type                 |
| ---------------------------------------------------------------------------------------------- | ------------------------------- |
| [Account Updater](https://docs.verygoodsecurity.com/cmp/products-and-services/account-updater) | On Create Card (Default)/Manual |
| [Network Tokens](https://docs.verygoodsecurity.com/cmp/products-and-services/network-tokens)   | On Create Card (Default)/Manual |