> 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/using-emv/performing-an-emv-transaction.md).

# Performing an EMV Transaction

EMV transactions progress in the following manner:

* **Card detection and reset:** In this phase:\
  Contact EMV: The Consumer inserts the card into the PIN pad. The terminal reads the data from the card and sends a message specifying how it will deal with the card. The Consumer does not remove the card at this stage.\
  Contactless EMV: When the Consumer taps or waves the card over the reader sensor, the terminal detects the chip in the card (using NFC), and sends a message specifying how the terminal must interface with the card.\
  *Even though with Contactless EMV, and Visa’s Quick Chip standard, the Consumer does not keep their card with the PIN pad (as they do when the card is inserted), the PIN pad may still display prompts for the Consumer to take action, such as selecting Credit or Debit, or requesting a Cashback. See “Types of EMV Transactions” below for more information.*
* **AID List Creation:** The card and terminal have lists of AIDs that they compare to find a match, which is also determined by any business rules that are in place. (Please see "Application ID Configuration" and "AID Rules" above for more information.)
* **AID Selection:** The terminal and card determine which AID they are going to use for the transaction.
* **Authentication and Risk Management:** The terminal uses the read chip data to verify that the card is genuine and not modified. and determines actions accordingly.
* **Online Processing:** The terminal sends the information to the card issuer, which checks the card status and determines whether to accept or reject the transaction.
* **Transaction completed:** After the card has been analyzed and the transaction accepted or rejected, the transaction finishes. For Contact EMV, the Consumer removes the card from the PIN pad at this stage.


---

# 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/using-emv/performing-an-emv-transaction.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.
