> 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/errors/not-detecting-inserted-cards.md).

# Not Detecting Inserted Cards

What to do when a V660P isn't reading inserted (chip) cards, including testing and cleaning the chip reader.

{% hint style="info" %}
**Use this page when** the terminal isn't reading cards inserted into the chip reader.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: cards not being detected, not detecting inserted cards, chip not reading, card not detected, chip reader not working. Search terms: card not detected, chip, chip reader, not reading, insert, card reader.

</details>

## Symptoms

You may see one or more of the following:

* Cards inserted into the chip reader aren't detected or read.
* The terminal doesn't respond when a card is inserted.
* Chip transactions fail, but contactless may still work.

**Most likely cause:** a dirty or faulty chip reader (or a damaged card).

## Resolution

{% stepper %}
{% step %}

### Check the card

Make sure the card is inserted **fully**, with the **chip first and facing up**. Try a **different card** to rule out a damaged chip.

✅ **Issue fixed — stop here.** ❌ **Still not working — continue to Step 2.**
{% endstep %}

{% step %}

### Test the chip reader

Run the card reader test to check whether the chip reader is working — see [How to Test the Chip Reader](/support-nordics/v660p/how-tos/how-to-test-the-chip-reader.md).
{% endstep %}

{% step %}

### Clean the chip reader

If the test fails, clean the reader:

1. **Power off the terminal.** Hold the **power button** until the device turns off.
2. **Clean the reader.** Take a card (ideally one with raised numbers). Insert it **upside down and back to front**, so the chip is **not** in the reader. Remove and reinsert it **10 times**, wiggling it each time to dislodge dirt inside the reader.
3. **Power the terminal back on.** Hold the power button until the device turns on.
4. **Try a test transaction** to confirm the chip reader is working.

✅ **Issue fixed — stop here.** ❌ **Still not working — see below.**
{% endstep %}
{% endstepper %}

## Still not working?

{% hint style="info" %}
**The chip reader may be damaged.**

If cleaning hasn't resolved it, <mark style="color:red;">contact Support to log a replacement terminal</mark>. In the meantime, you can still take payments by **contactless** or another method.
{% endhint %}


---

# 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/errors/not-detecting-inserted-cards.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.