> 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/application-id-configuration.md).

# Application ID Configuration

Application IDs represent the card types supporting EMV processing, and systems that process EMV transactions must specify which AIDs the system can process.

{% hint style="warning" %}
*Merchants cannot add additional AIDs, and disabling an AID is not recommended. Disabling an existing AID could leave the merchant liable for transactions that should otherwise use that AID.*
{% endhint %}

In order to process a card transaction as an EMV transaction, there must be an AID match between the system's AIDs and the card's (i.e. the same AID must be present on both). The AIDs available on the system are specified by the Acquiring Hosts and placed in the EMV processing terminal by VIPER. The Acquiring Host can only accept the AIDs they have communicated to the system.

**Ensure that when EMV is being enabled, AIDs are listed in the system and are enabled.**

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

1. The **AID** alpha-numeric string is supplied by the acquiring host and may be a full or partial AID. Merchant level configuration is not available for this field.
2. The **AID Name** is associated with a card type supporting EMV processing and is provided by the acquiring host. The AID Name displays on the PIN pad if an AID selection menu is presented. Merchant configuration is not available for this field.
3. The **AID \<Enable>** checkbox allows selecting to enable the AID. The AID may be disabled if the merchant should desire. Verifone discourages disabling an AID as this could lead to Merchant liability for transactions that should have been processed through EMV using the AID.
4. **\<Bypass PIN>** Entry is an optional EMV function that if enabled may be invoked when the following occurs:
   * The terminal prompts the cardholder for a PIN.
   * The cardholder opts to not enter the PIN and invokes this function For these transactions, the approving host is notified with a transaction indicator that the PIN was manually bypassed on a PIN-preferring card.
5. **\<Account Type>** configuration allows selection for the transaction type associated with the AID: Credit Only, Debit Only, Credit & Debit. This configuration option can lead to additional Credit/Debit prompting in the transaction flow. In most cases this value will come from the VIPER table owner.


---

# 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/application-id-configuration.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.
