# EMV Settings

EMV configuration is a set of rules, security keys, and card-brand parameters that allow the device to process chip-card transactions securely.

## EMV Inside and Outside

EMV is configured Inside and Outside.

<figure><img src="/files/xAGbP94AsZUEKT00eX4t" alt=""><figcaption></figcaption></figure>

## EMV AID Configuration

AIDs tell the Verifone Commander which EMV applications it can use to process chip cards. Each AID matches a card brand or network, ensuring the terminal follows the right rules and security steps. Without the correct AIDs, some chip cards may not process correctly.

<figure><img src="/files/esI6i1Tx5uMjcvDATySn" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="154" valign="top">Field/Button</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">AID Name</td><td valign="top">A label for the EMV application associated with a card brand (e.g., Visa, Mastercard). Helps identify which application the terminal will use when a chip card is inserted.</td></tr><tr><td valign="top">Contact</td><td valign="top">Indicates whether the AID is enabled for contact (chip-insert) transactions. If disabled, the terminal won’t use that AID for chip-insert processing.</td></tr><tr><td valign="top">Contactless</td><td valign="top">Indicates whether the AID is enabled for contactless (tap) transactions. If disabled, the terminal won’t use that AID for tap-to-pay.</td></tr><tr><td valign="top">PIN Bypass</td><td valign="top">Controls whether the terminal allows a customer to skip entering a PIN when prompted. Often used for low-value transactions or specific merchant preferences</td></tr><tr><td valign="top">Stand-in</td><td valign="top">Determines whether the terminal can approve certain transactions locally when it can’t reach the host. Useful for keeping transactions flowing during brief communication outages</td></tr></tbody></table>

{% stepper %}
{% step %}
**Card Settings**

Click on a card to display the settings.
{% endstep %}
{% endstepper %}

<figure><img src="/files/eBCBbfF6Lrqu6D4qCIkh" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th valign="top">Field/Button</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top"><strong>General</strong></td><td valign="top"></td></tr><tr><td valign="top">AID</td><td valign="top">Specifies the Application Identifier used to route and process EMV transactions.</td></tr><tr><td valign="top">AID Name</td><td valign="top">A label for the EMV application associated with a card brand (e.g., Visa, Mastercard). Helps identify which application the terminal will use when a chip card is inserted.</td></tr><tr><td valign="top">PIN Bypass</td><td valign="top">Allows the customer to complete a transaction without entering a PIN when permitted.</td></tr><tr><td valign="top"><strong>Stand-in</strong></td><td valign="top"></td></tr><tr><td valign="top">Stand-in</td><td valign="top">Enables fallback authorization when the host system is unavailable.</td></tr><tr><td valign="top">Allow Foreign Cards</td><td valign="top">Permits the terminal to accept cards issued outside the local region.</td></tr><tr><td valign="top">Floor Limit</td><td valign="top">The maximum transaction amount allowed before requiring online authorization.</td></tr></tbody></table>

{% stepper %}
{% step %}

### Back&#x20;

Click the Back button to return to the card list in the AID Configuration.
{% endstep %}
{% endstepper %}

## EMV CAPK Configuration

{% hint style="info" %}
EMV CAPK Configuration is Read-Only. Information is sent from the Verifone Commander.
{% endhint %}

CAPK configuration loads the public keys the Verifone Commander uses to verify a chip card during offline authentication. Each card brand has its own CAPKs, and the terminal must store them to validate EMV digital signatures. Keeping CAPKs updated ensures the terminal can trust chip data and reject counterfeit cards.

<figure><img src="/files/BR2QZXXWY03vpkon2q2O" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th valign="top">Field/Button</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">CAPK ID</td><td valign="top">A unique identifier for a specific public key used by a card brand. It tells the terminal which key it’s working with during EMV authentication.</td></tr><tr><td valign="top">RID (Registered Application Provider Identifier</td><td valign="top">A 5-byte identifier assigned to each card brand or payment network. It groups CAPKs by brand (e.g., Visa, Mastercard, American Express).</td></tr><tr><td valign="top">Index</td><td valign="top">A 1-byte value that distinguishes different keys under the same RID.Since a brand can have multiple CAPKs,, the index tells the terminal which exact key to use.</td></tr><tr><td valign="top">Expiry</td><td valign="top">The date when the CAPK is no longer valid. Terminals must remove or replace expired keys to ensure secure EMV authentication</td></tr></tbody></table>

## Commander Payments

### U.S. Debit Rules

<figure><img src="/files/1e0zEZlwDv9rdxHOykcC" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="233" valign="top">Field/Button</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">Select Configuration Type</td><td valign="top">Choose the EMV profile based on whether the terminal operates inside the store or at an outdoor payment point.</td></tr><tr><td valign="top">US Debit - PIN Preferring</td><td valign="top">Prioritizes PIN-based authentication for US Debit transactions when available.</td></tr><tr><td valign="top">US Debit - No PIN</td><td valign="top">Allows US Debit transactions to process without requiring a PIN when permitted by the card and network.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/payment-operations/emv-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
