> 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/bluefin-encryption/configuring-bluefin-encryption/eps-and-pin-pad-configuration.md).

# EPS and PIN pad Configuration

**EPS**

There is no configuration required. After the 56.03 software is installed, EPS automatically detects whether any PIN pad is P2PE enabled. On detecting that any PIN pad is P2PE enabled EPS considers that P2PE is active at the site. After P2PE is active at a site, EPS will not allow any network transactions from a POS that is associated with a non P2PE PIN pad.

**PIN Pad**

1. Installing 56.03 will automatically get all the PIN pads at the site upgraded to EVPAY 2.08.00 R09.

To enable P2PE functionality on the PIN pad below two steps are required. These are only required to be done for the initial setup. After a PIN pad is P2PE enabled, it cannot be revered back to non-P2PE mode.

1. Install FET package to enable P2PE (e.g: ADE-FE-VOS-PROD-WAW-Token.tgz).
2. Install Bluefin production ADE keys for encryption (e.g: BMX\_1-25-0011-5598.tgz).

Steps 2 and 3 can be done remotely from VHQ or manually at a site by VASC using USB pen drive. P66 is responsible for installing the packages on the PIN pad.

The cashier should log off and log in to the POS after P2PE is enabled on the PIN pad.

{% hint style="info" %}
The FET and ADE packages names are for reference only, the actual package names might be different.
{% 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/bluefin-encryption/configuring-bluefin-encryption/eps-and-pin-pad-configuration.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.
