> 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/configuring-emv/advanced-configuration/aid-rules.md).

# AID Rules

{% hint style="warning" %}
*Implementing AID Rules should be considered advanced configuration and only undertaken by individuals with a complete understanding of AID selection.*

*Verifone is not responsible for AID Rule configurations. Contact the Front-End Processor and Merchant Service Provider to assist with determining AID order for rules.*
{% endhint %}

The EMV Application ID selection occurs immediately after the Consumer inserts their card. When the card is inserted, the terminal must determine what AIDs are mutually supported between the card chip and the terminal, then select an AID to process the transaction.

For Debit Cards, or when there is more than one AID that is mutually supported between the chip card and the terminal, a choice must be made regarding which AID to select to process the transaction.

AID Rules allow setting preferences for a selected AID over others by configuring a Rules List.

The AID Rules section allows creating the Rules List to define a set of preferred AIDs for use during the AID selection phase.

The functionality is specifically designed to support the U.S. Common Debit AID, allowing the Common AID to be selected by default when multiple AIDs are present.

Multiple AIDs can be included when creating an AID Rule. When viewing a Rule Exclusion List, selection preference is given to the included AIDs from left to right.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/UaC2vMv6M7GezZQjSpTh/Unknown%20image)


---

# 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/configuring-emv/advanced-configuration/aid-rules.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.
