> 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/troubleshooting-emv/no-transactions-processing-as-emv-transactions.md).

# No Transactions Processing as EMV transactions

1. See the section for Enabling EMV, and verify EMV is enabled.
2. Use the EMV Configuration Report or check the Configuration Client EMV Initialization tab to verify that the EMV configuration has been pushed to the PIN pads.
3. Confirm that AIDs exist in the AID list.

If there are no AIDs, EMV cannot process cards. AIDs cannot be site configured and must be either part of the distribution or downloaded by the table owner. If there are no AIDs present in the system, make sure the system has performed a PDL or Table Download, whichever is appropriate for the FEP.

4. Confirm that CAPKs exist in the CAPK list and are not expired.

If there are no CAPKs, or if CAPKs are expired, EMV cannot process cards correctly. CAPKs cannot be site configured and must be either part of the distribution or downloaded by the table owner. If there are no CAPKs present in the system, make sure the system has performed a PDL or Table Download, whichever is appropriate for the FEP. If there are expired CAPKs present in the system, perform a PDL or Table Download, as appropriate for the FEP.

5. Confirm network connectivity as network communications issues could also cause problems.


---

# 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/troubleshooting-emv/no-transactions-processing-as-emv-transactions.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.
