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

# EMV Configuration Report

The EMV Configuration Report contains general EMV configuration data for each Terminal ID including the following:

* Last PIN pad Configuration Time
* Terminal Type
* Terminal Capabilities
* Country Code
* Currency Code
* Transaction Category Code
* Merchant Category Code

This data is set for each installation instance (FEP) and is not site configurable. The information is provided as informational only.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fz4ZjVH8rgRVo7KW8QtfQ%2Fimage.png?alt=media&amp;token=62c382d9-e18b-4f69-81bd-0cd4ed278657" alt=""><figcaption></figcaption></figure>

The EMV Configuration Report also contains each Application Identifier's specific configuration. Information provided for each AID includes the following:

* AID Label (will be used if an AID menu is required)
* AID code
* AID floor limit (important for offline processing)
* other configurations unique to each AID.

The report will contain a section for each AID configured in the system. A sample report is provided. Actual printed reports may vary.

Sample EMV Configuration Report, AID Specification

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FGiX3x8hiG5pUDCblLJxa%2Fimage.png?alt=media&amp;token=038332fa-2544-4ef2-b820-e53c365d5011" alt=""><figcaption></figcaption></figure>


---

# 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://docs.verifone.com/feature-references/features-and-products-references/emv-inside-emv/reporting-emv/emv-configuration-report.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.
