> 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/normal-inside-emv-flow.md).

# Normal Inside EMV Flow

1. Consumer brings goods or service requests to the Cashier.
2. The Cashier rings up the goods and services. This can include both prepay and post-pay fuel sales and non-fuel items.
3. **Contact EMV**: The Consumer inserts the EMV card into the PIN pad's EMV card reader. The card remains in the chip reader for the duration of the transaction while the chip is read and while any customer verification prompting is performed. When the EMV card processing is finished, the consumer will be notified to remove the card. In Verifone's Quick Chip flow, the card does not need to remain in the reader for the duration of the transaction. Card insertion, like the MSD swipe ahead, can be done at any time.\
   **Contactless EMV**: After being prompted to tap or wave, he Consumer waves or taps the EMV card against the PIN pad's wave/tap card reader. The card only needs to be in proximity to the sensor long enough for the reader to obtain the required data. Reading the card chip is the first interaction between the PIN pad and the chip on the card.

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FUSP3K43jVF10S8hWGX2Z%2Fimage.png?alt=media&amp;token=760a7cea-f255-49a4-8f64-c50e69e4da0c" alt=""><figcaption></figcaption></figure>
4. The Cashier tenders the transaction for network payment the same as would be done for MSD tendering.
5. The "Network tender" triggers a request for payment to VIPER, which in turn communicates with the PIN pad to process the EMV payment request. This step in EMV processing is referred to as the First Generate AC.\
   • The 1st Gen AC is the second communication, after the read, with the card. The 1st Gen AC performs the CVM processing and results in either an offline approval, a request to go online, or a decline. The results of the CVM processing are also returned.
6. VIPER uses card data from the Contact or Contactless EMV card and transaction information from the POS to obtain payment authorization from the payment host.
7. If the transaction is approved, the Approval is indicated to the Consumer and the Cashier.
8. Contact EMV only: Note that the receipt will not print and the transaction will not clear from the POS until the Consumer removes their card. The Cashier should prompt the Consumer to remove the card if they do not do so in a timely manner following the transaction approval.
9. The receipt prints and the transaction is cleared from the POS.


---

# 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/normal-inside-emv-flow.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.
