Cards
...
Partner-managed model
Add identification
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 docid\ isgkj7nis9jhmyu3upubk endpoint for more details 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 { "isprimary" false, "idnumber" "\<token value goes here>", "idtype" "other", "issuingauthority" "token", "issuingcountrycode" "us" { see our tutorial which explains how to docid\ gk2ctwkzvsjntrdhq67e5 as always, if you have any questions, email our mailto\ cos support\@crossriver com team