> 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/configuring-emv/basic-configuration/updating-pin-pads.md).

# Updating PIN pads

{% stepper %}
{% step %}
Log out of Sales mode and back in to Sales mode on the POS. The PIN pad will download the new EMV tables when you do so.
{% endstep %}

{% step %}
Verify that the EMV card slip is lit up on the PIN pad.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FhwmaN8sz5q5e9mbosYLc%2Fimage.png?alt=media&amp;token=f72d0ce2-be83-4202-b1f0-6a1aef44179f" alt=""><figcaption></figcaption></figure>

If the PIN pad was not initialized by logging into Sales mode, you can also use the process below to manually initialize individual PIN pads.
{% endstep %}

{% step %}
Navigate to Payment Controller > EPS Configuration > EPS Global Configuration > EMV Initialization.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fm6WNtTssjHWTuwJJcLgn%2Fimage.png?alt=media&amp;token=3ea552e3-e734-4d17-afc7-4309ea36b664" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
The list of PIN pads that did not update will appear in the Available POP List. Select all PIN pads from the Available POP List, and move them to the Selected POP List using the **\[Add>>]** or **\[Add All]** buttons. This will instruct the system to update the PIN pads.
{% endstep %}

{% step %}
Click **\[Save]** to force an initialization through to the selected PIN pads.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FYIh7yzodfLU19ZuLP2CT%2Fimage.png?alt=media&amp;token=7e628f5d-f4c2-4c6d-92c7-adde026558ad" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
*In the event PIN pads are not listed in the POP Configuration Status panel on the EMV Initialization screen, see the Troubleshooting section for more information. PIN pads listed here may not be receiving the proper configurations to run EMV transactions.*
{% 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/configuring-emv/basic-configuration/updating-pin-pads.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.
