> 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.md).

# Configuring EMV

By default, the Verifone site controller is installed with EMV disabled. How EMV is enabled at the site varies depending on the card processor. Some card processors require an EMV-specific download in order to activate EMV. Others, such as Buypass, may require EMV to be enabled within the site controller's payment controller configuration.

Contact your payment network for more information on enabling EMV at the site level.

{% hint style="info" %}
*Refer to the Network-specific EMV Configuration Guide and/or contact the site’s Electronic Payment Host Provider for additional details on configuring your Verifone solution for EMV.*
{% endhint %}

If your payment network requires EMV to be enabled on the site controller, proceed to the next section. All site-controller enabled EMV configurations are done through Configuration Client.

## **Verifone Commander**

Access the Configuration Client for Verifone Commander at the URL provided by your VASC, or by logging into the Configuration Manager in the CSR Functions on the register. Login to Configuration Client using the Manager login name and current password.

* User Name: Manager
* Password: (\*\* the current valid Manager password \*\*)


---

# 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.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.
