Tagging an existing card for sending to Account Updater provider

Background
Before starting this tutorial, make sure you understand the following topics from the Quick start section: Sandbox environments (especially about testing). Authentication (about authenticating using your API user and when you need a login versus a one-time-use token).

Update the Card's Registration Tag

Send a PUT request to the Update card token endpoint. Include the parameter shouldUpdateCard: true in the body of your request.

curl -X PUT https://api.nexiopaysandbox.com/pay/v3/vault/card/{cardToken} \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic [Base64_encoded_login]'
  -d '{
  "shouldUpdateCard": true
}'

Check the Card's Status (Optional)

Send a GET request to the View card token details endpoint.
For legacy accounts, the response includes a string value called accountUpdaterStatus (see the account updater Card status table for more information). For current accounts, the response includes the shouldUpdateCard parameter. This is the card's enrollment status.

📘
Note
It usually takes three to four business days for a card token to become registered with account updater.
```
curl -X GET https://api.nexiopaysandbox.com/pay/v3/vault/card/{cardToken} \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic [Base64_encoded_login]'
```
```
{
  "accountUpdaterStatus": "isExcluded",
  "card": {...},
  "data": {...},
  "dateCreated": "2019-07-31T17:02:39.035Z",
  "dateLastModified": "2019-07-31T18:33:30.660Z",
  "merchantId": "100100",
  "shouldUpdateCard": true,
  "tokenex": {...}
}
```

Updated about 1 year ago

📘Note

📘
Note