> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-inside-emv/troubleshooting-emv/cleaning-process.md).

# Cleaning Process

Inspect -- First, visually inspect the terminal's Smart Card Reader before attempting o clean the unit. All debris, "foreign objects," and other material must be removed from the Smart Card Reader before using the cleaning cards.

Pre-Test -- If no debris is found in the Smart Card Reader, run the internal Smart Card test using the following steps.

* If an application is already loaded and running, put the terminal into System Mode by pressing keys 1, 5, 9 at the same time. If there is no application loaded, the terminal will boot up to the System Mode Login Screen.
* Navigate to Diagnostics > Card > Smart Card. Insert a card before selecting the tab.
* If the terminal passes the diagnostic test, proceed to the next step.
* If the terminal fails the diagnostic test, make a note of the failure and proceed to the next step.

Cleaning -- Use the Smart Card Reader Cleaning Kit (Verifone PN 02746-02).

Test After Cleaning -- Retest the Smart Card reader in Diagnostic mode using the instructions in step 2.

* If the terminal fails the Smart Card Reader Test, send the terminal in for repair.
* If the terminal passes the Smart Card Reader Test, reboot the terminal's application for regular use.


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-inside-emv/troubleshooting-emv/cleaning-process.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.
