> 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/reporting-emv/emv-transaction-statistics-report.md).

# EMV Transaction Statistics Report

The EMV Transaction Statistics Report shows all EMV transaction data by Terminal Batch Number for each PIN pad, designated by the Terminal ID. Grand totals for all PIN pads are also included. The report allows the site to track the following transaction data:

* Total EMV Transactions, shown as ICC (Integrated Card Chip)
* EMV Magstripe Fallback, shown as ICC Fallback Swipe
* Swiped (normal MSR)
* Manual Keyed
* RFID Contactless (non-EMV)

A sample report is provided. Actual printed reports may vary.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fnwjsvfzqe3lQx7hXhbby%2Fimage.png?alt=media&amp;token=d8cee60b-f4dd-4306-a47f-5b8860f584ee" 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://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-inside-emv/reporting-emv/emv-transaction-statistics-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.
