> 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/emv-initialization.md).

# EMV Initialization

The EMV Initialization tab allows forced initialization on selected POP devices, and provides confirmation of any PIN pad updates that have failed. The Initialize POP process is performed automatically for each PIN pad in the system during initial EMV implementation, which is initiated through a PDL or table download. The POP Configuration Status Panel keeps track of what data has been sent and any error messages that may have occurred. Utilizing the Initialize POP function is only required for new PIN pad terminals that are introduced to a running system, or if errors are detected and shown in the POP Configuration Status panel.

## **Initialize POP**

1. Navigate to Payment Controller > EPS Global Configuration > EMV Initialization
2. Click to select and highlight the POP ID(s) to be initialized from the Available POP List. ![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/asaVzYPFRgeuqojHUwuQ/Unknown%20image)
3. Click \[Add>>] or \[Add All] to move the AID(s) to the Selected AID List. ![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/ecfTBPlQJGQoQKyZNcsl/Unknown%20image)
4. Click \[Save] to initialize the selected POP devices for EMV use. ![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/sGfdM9S2sJE2lMiKgPSJ/Unknown%20image)

{% hint style="info" %}
*Do not navigate away from the* EMV Initialization *tab before saving, unless you wish to cancel the initialization. Once the user navigates away from the* EMV Initialization *tab, the page is reset.*

*Without saving, all POP devices will be displayed in the*

Available POP List *again.*

*Initialization of selected PIN pad(s) occurs with the corresponding* SAVE\_.\_
{% 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://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-inside-emv/troubleshooting-emv/emv-initialization.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.
