> 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-nordics/v660p/how-tos/how-to-test-the-chip-reader.md).

# How to Test the Chip Reader

Run the card reader test on your V660P to check the chip reader is working, and clean the reader if needed.

{% hint style="info" %}
**Use this when** you need to check whether the chip (card) reader on your V660P is working.
{% endhint %}

## Run the card reader test

{% stepper %}
{% step %}

### Open Diagnostics

1. Open the app list: swipe **up** on the home screen. If your V660P opens straight into **Connect Express**, swipe **down** from the top of the screen and tap the **settings icon** in the bottom-right corner to get to the Android menu.
2. Tap **Diagnostics**.

<figure><img src="https://2708971099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fa0qV9Wx6LdSaDc8JrEef%2Fuploads%2FormcBX9cfdOIxZGCx7Yg%2Fchip-diagnostics-menu.png?alt=media" alt="Diagnostics menu" width="180"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Open the Card Reader Test

Scroll down and select **Card Reader Test**.

<figure><img src="https://2708971099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fa0qV9Wx6LdSaDc8JrEef%2Fuploads%2F1pfRkORiqlV7SCF9I4tE%2Fchip-card-reader-test.png?alt=media" alt="Card Reader Test option" width="235"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Insert a card and check the result

Insert a card when asked. The test shows whether the chip reader is working.

<figure><img src="https://2708971099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fa0qV9Wx6LdSaDc8JrEef%2Fuploads%2FFxWj1I7yGwAzAwzABdCP%2Fchip-test-result.png?alt=media" alt="Card reader test result" width="240"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## If the test fails: clean the chip reader

{% stepper %}
{% step %}

### Turn off the terminal

Hold the **power button** for about **1 second**, then tap **Power off**.
{% endstep %}

{% step %}

### Clean the reader

Take a card — ideally a debit or credit card with raised numbers. Insert it **upside down and back to front**, so the chip is **not** in the reader. Remove and insert it **10 times**, wiggling it each time to dislodge dirt inside the reader.
{% endstep %}

{% step %}

### Turn the terminal back on

Hold the **power button** for about **2 seconds** until the start screen appears.
{% endstep %}

{% step %}

### Try a test transaction

Take a small test payment by inserting a card, to check the chip reader is working.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Still not working?** The chip reader may be damaged — see [Not Detecting Inserted Cards](/support-nordics/v660p/errors/not-detecting-inserted-cards.md) and <mark style="color:red;">contact Support to log a replacement terminal</mark>. In the meantime, you can still take **contactless** payments.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: card reader test, chip reader test, test card reader, chip not reading, clean chip reader. Search terms: chip reader, card reader, test, diagnostics, clean, insert, chip.

</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-nordics/v660p/how-tos/how-to-test-the-chip-reader.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.
