> 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/t650-two-piece/how-tos/how-to-test-the-chip-reader.md).

# How to Test the Chip Reader

Test the P400's chip reader with a test card payment, and clean the reader if cards aren't being read.

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

Your customer inserts their card into the **P400**, so the chip reader can only be tested on the P400.

## Test the chip reader

{% stepper %}
{% step %}

### Start a small test payment

On the T650C, enter a small amount and tap **Card** — see [How to Process a Sale](/support-nordics/t650-two-piece/how-tos/how-to-process-a-sale.md).
{% endstep %}

{% step %}

### Insert a card into the P400

When the P400 shows the payment screen, **insert** a chip card fully, with the **chip first and facing up**.

* **If the card is read and the payment continues:** the chip reader is working.
* **If the card isn't detected:** try a **different card** to rule out a damaged chip. If that doesn't work either, clean the chip reader below.
  {% endstep %}
  {% endstepper %}

## Clean the P400's chip reader

{% stepper %}
{% step %}

### Clean the reader

Take a card — ideally a debit or credit card with raised numbers. Insert it into the P400 **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 %}

### Restart the terminal

Restart the T650C — see [How to Reboot the Terminal](/support-nordics/t650-two-piece/how-tos/how-to-reboot-the-terminal.md). The P400 restarts with it.
{% endstep %}

{% step %}

### Test again

Start another small test payment and insert a card into the P400 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/t650-two-piece/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, P400, PIN pad, clean, insert, chip, test payment.

</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/t650-two-piece/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.