> ## Documentation Index
> Fetch the complete documentation index at: https://docs.polygon.technology/llms.txt
> Use this file to discover all available pages before exploring further.

# Customers

> Identity records that own wallets, accounts, and transactions in OMS.

A customer is the top-level identity record in OMS. Every wallet belongs to a customer, and associated concepts such as virtual accounts, deposit addresses, and external accounts (currently early access) are tied to the customer as well. No financial operation can happen without one.

## Object

```json theme={null}
{
  "id": "cst_...",
  "status": "active",
  "endorsements": ["basic", "usd"],
  "createdAt": "2025-01-15T10:30:00Z"
}
```

## Endorsements

Endorsements gate which operations a customer can perform. OMS grants them after KYC/KYB verification.

| Endorsement     | Unlocks                              |
| --------------- | ------------------------------------ |
| `basic`         | Standard operations                  |
| `cryptoCustody` | Crypto custody and advanced features |
| `usd`           | USD stablecoin operations            |

Endorsements are granted asynchronously. Listen for the `customer.endorsement.granted` webhook before attempting operations that require a specific endorsement.

## Lifecycle

```
POST /customers  →  created
                      │
            KYC/KYB verification
                      │
                      ▼
         customer.endorsement.granted  →  operational
```

Create the customer record first, then initiate your KYC/KYB flow. OMS handles compliance screening; your application handles identity collection.

## Key operations

| Operation           | Endpoint                      |
| ------------------- | ----------------------------- |
| Create a customer   | `POST /customers`             |
| Retrieve a customer | `GET /customers/{customerId}` |
| List customers      | `GET /customers`              |

## Related

* [Customer onboarding guide](/payments/guides/customer-onboarding): full walkthrough including KYC flow and webhook handling
* [Wallets](/payments/wallets): provision wallets once the customer is endorsed
* [Compliance](/payments/compliance): KYC/KYB requirements by corridor