> 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-stand-in-configuration.md).

# AID Stand-In Configuration

{% hint style="warning" %}
*Verifone recommends the* Stand-In TVR Mask *field remain unchanged unless the person editing the configuration is an EMV Expert, and fully understands the ramifications of updates to this field.*
{% endhint %}

As with traditional MSR processing, EMV based transactions may allow stand-in processing to approve transactions even if the online payment host is offline and not available. EMV data in a transaction allows the system to consider many conditions when making a decision to stand in for a transaction. The system still uses the traditional Magnetic

Swipe Read (MSR) data points, but additional EMV data allow for much finer decision points for consideration.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FTzcfEUEDPzsdg5tBVsOG%2Fimage.png?alt=media&amp;token=3569a36a-cbfc-433d-819b-41228e1a0378" alt=""><figcaption></figcaption></figure>

The AID Configuration panel provides the following:

* The **\<Allow Stand-In for AAC>** setting tells the system whether to allow offline processing for the AID. If this box is left unchecked, stand-in processing is disabled for the card types associated with the AID.\
  When Stand-In Processing is turned off for an AID, no offline authorizations will be allowed for any transaction, regardless of what other criteria are present.
* The **\<Stand-In TVR Mask>** field allows editing mask definitions that will be logically *ANDed* with the Terminal Verification Results. If this logic results in a non-zero result, the system will not stand-in for the transaction.\
  In the example image shown below, the Stand-In TVR Mask value is 80008000. If Offline Data Authentication is not performed, or Cardholder Verification is not performed, the transaction will be declined.

  <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FIX6S2JqQ4SfxHeA40oRJ%2Fimage.png?alt=media&amp;token=dbe1b190-91af-4a40-b0fe-d0c7bf02c3d2" alt=""><figcaption></figcaption></figure>

See EMV 4.3 Specification Book 3, at [www.emvco.com/specifications.aspx?id=223](http://www.emvco.com/specifications.aspx?id=223) for details of the five-byte binary bitmap TVR.

* The **\<Stand-In TSI Mask>** field operates like the TVR mask but is logically *ANDed*

  with the Transaction Status Information.
* The **\<Stand-In Country Code Check>** controls the acceptance of foreign cards. When enabled, the terminal’s country code is compared with the card’s AID country code. If the codes match, the transaction will be approved in stand-in.
* The **\<Stand-In Floor Limit>** allows setting a dollar amount, such that no transactions over the set Floor Limit will be approved. If the Floor Limit is set to zero (0), that essentially turns off any stand-in option for that AID.

  This value is separate from the floor limit present on the card.


---

# 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-stand-in-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.
