> 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/support-us/general-pinpad-support/general-pinpad-help/tamper-errors.md).

# Tamper Errors

Troubleshooting tamper errors on Verifone devices and how to resolve them.

{% hint style="info" %}
**Use this when** a device shows a tamper error.
{% endhint %}

## Symptoms

A tamper error can result from physical damage, such as:

* A power surge
* Dropping the device
* A liquid spill
* Loose components inside the device
* General physical damage

**Most likely cause:** physical damage to the device.

## Resolve the error

{% hint style="danger" %}
A device showing a tamper error **must be replaced** — this indicates physical damage that can't be resolved through troubleshooting on-site.
{% endhint %}

{% stepper %}
{% step %}

### Arrange a replacement

Contact your Merchant Services Provider, Reseller, or, if applicable, Verifone to arrange equipment replacement.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
See Order Equipment to learn more about replacing equipment.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: tamper alert, tamper detected, physical damage error. Search terms: tamper error, device replacement.

</details>


---

# 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/support-us/general-pinpad-support/general-pinpad-help/tamper-errors.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.