> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/asset-tracking/updating-the-file-chain-of-custody.md).

# Updating the File Chain of Custody

Record a custody handoff, status update, inspection result, or incident for one device.

Use **File Chain of Custody** to update one device's custody details during asset tracking.

Use it to record a handoff, status change, location update, inspection result, or incident.

### Before you start

Confirm that you know:

* the target device and its current custody stage
* the status, location, or inspection details you need to record
* whether you need to add notes or upload supporting images

Prepare these details when available:

* device **Serial Number**
* current or new custodian
* current or new location
* expected status
* inspection notes and image files

Match the device serial number to the physical device before you change custody data.

### Open File Chain of Custody

{% stepper %}
{% step %}

### 1. Open the device from **View Devices**

Go to **Device Management** → **Devices** → **View Devices**.

<div data-with-frame="true"><figure><img src="https://1786380399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdzivQyj8aHN5Kvmx8apX%2Fuploads%2FVayijHrb68gnzfSTitID%2FPicture160.png?alt=media&amp;token=26f59485-30e3-4396-84bc-f294a1df63d4" alt=""><figcaption></figcaption></figure></div>

Select the device you want to update.
{% endstep %}

{% step %}

### 2. Or open the device from **Chain of Custody**

Go to **Device Management** → **Reports** → **Chain of Custody**, search for the device, and open the record.

<div data-with-frame="true"><figure><img src="https://1786380399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdzivQyj8aHN5Kvmx8apX%2Fuploads%2F0G5yuGr10GP7mvo3nkfF%2FPicture161.png?alt=media&amp;token=d10b7a14-41e4-44f7-be74-a964c81aa28d" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### 3. Open **File Chain of Custody**

From **Device Details**, select **File Chain of Custody**.

<div data-with-frame="true"><figure><img src="https://1786380399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdzivQyj8aHN5Kvmx8apX%2Fuploads%2FwJx3nKu3qhiWyIpJopA6%2FPicture162.png?alt=media&amp;token=23ffd83d-4153-45ed-9469-8af8a86b35a7" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
You can reach **Device Details** from either **View Devices** or **Chain of Custody**.
{% endhint %}

### Review the page sections

#### General Information

Use this section to confirm the record before you change anything.

These fields are informational:

* **Device Serial Number** — read-only
* **Device Tamper Label ID Number** — the tamper label on the device
* **Shipment Tracking Number** — populated during shipment from the Verifone store

#### Chain of Custody

Use this section to record the new custody state.

Select the status that matches the physical device state:

* **Awaiting deployment** — the device is received by a trusted custodian and stored securely, but not installed yet
* **Deployed** — the device is installed and actively used for payment transactions
* **In Repair** — the device has malfunctioned and has been sent to an authorized repair center
* **Malfunctioning** — the device has a fault, but it has not yet been shipped for repair
* **In-Transit** — the device is moving between approved locations
* **Retired** — the device is removed from service and will not return to operation
* **Lost or Stolen** — the device cannot be accounted for
* **Tampered** — the device or tamper-evident seal shows tamper evidence or a tamper message

You can also update:

* **Location** — choose the current approved location
* **Device Last Known Telemetry** — review the pre-populated previous custodian, location, and status values before saving

Compare the prior telemetry with the intended update. Stop if the visible record does not match the device or handoff you observed.

#### Device Inspection

Use this section when the custody event also needs an inspection record.

Inspection is typically recorded during:

* **In-Transit Inspection** — while the device is moving between locations
* **Periodic Inspection** — after the device is deployed and active

For inspection:

* answer **Yes** or **No** to whether the device shows no tamper or physical damage
* if the device passes inspection, record any relevant notes
* if the device does not pass inspection, answer the follow-up tamper and physical damage questions

Tamper review can include checks such as:

* a tamper message on the screen
* physical tamper on the device body
* cable or connection tamper
* damaged or tampered labels

Physical damage review can include checks such as:

* screws out of place
* discolored casing
* visible marks on the device
* signs of a skimmer or other theft device

If needed, upload supporting images in **png**, **jpg**, **jpeg**, or **gif** format and add details in **Notes**.

{% hint style="info" %}
Contact the **Solution Provider's Helpdesk** with the device serial number when you need to report an incident.
{% endhint %}

### Review before saving

Confirm the status, location, inspection answers, and notes describe the same physical event.

Do not mark a device **Deployed** before installation is confirmed. Do not mark it **Lost or Stolen** or **Tampered** without the supporting incident details.

### Verify the result

After you save the update, confirm that:

* the status matches the physical device state
* the custodian and location values are correct
* inspection answers, notes, and images are complete when needed
* the record now supports the next action in the workflow
* reopening the record shows the new event against the correct serial number

### Result

You can update one device's custody record with the status, location, inspection, and incident details needed for asset tracking.

### Next steps

* [View device status in Chain of Custody](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/view-device-status-in-chain-of-custody) — review the updated record
* [Configure locations](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/configure-locations) — maintain custody location values
* [Registering the device](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/registering-the-device) — continue after deployment


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/asset-tracking/updating-the-file-chain-of-custody.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.