---
title: Add identification
slug: concepts/cards/card-lifecycle/partner-managed-lifecycle/add-id-details
description: Cross River adds tokenized card numbers from processors and networks to COS customer records to track card info and usage for each cardholder.
docTags: 
createdAt: 2025-03-20T09:56:08.883Z
---

## Add identification intro

Cross River receives files from processors and from the networks that contain tokenized card numbers identifying each cardholder. We need to add these unique user identifiers to the COS customer record of each cardholder. This allows Cross River to track all the information that the card networks need to know about that customer's card and how they use it.

The Transaction Monitoring (TM) system, SAS AML, links transactions to customers by matching the tokens on transaction records against the Identifications entity in COS. This is the specific data source the AML pipeline reads from,  it does not pull from the Client Identifier field, *user\_id*, or any custom report fields. The only way to populate the Identifications entity is through the /identifications API endpoint. See the [Add personal customer](docId\:isgkj7NIS9jHmyu3UPUBk)  endpoint for more details.

:::hint{type="warning"}
**IMPORTANT**: If the endpoint is not populated and there is no feed into the AML linking process, meaning transactions would remain unattributable to customers.
:::

## Identifier

Add the identifier to the Customer ID section with this endpoint:

`POST /core/v1/cm/customers/{id}/identifications`

Use these values in the body of the request:

```curl
{
"isPrimary": false,
"idNumber": "<token value goes here>",
"idType": "Other",
"issuingAuthority": "TOKEN",
"issuingCountryCode": "US"
{
```

See our tutorial which explains how to [Add identification](docId\:Gk2cTwkzVsjNTRDhQ67E5).

As always, if you have any questions, email our [support](mailto\:cos.support@crossriver.com) team.&#x20;