> 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/age-restriction/configuring-age-restriction.md).

# Configuring Age Restriction

## Configuring Customer ID Check

Use **Store Operations > Restrictions > ID Checks**to set up, delete, or edit Customer ID Checks.

Use Customer ID Check form to define the age identification requirements that a customer may have to meet to purchase a product.

The ID check feature also captures expiration date information from the ID bar code or the magnetic stripe and perform an automated check to ensure that the ID is not expired. If the ID is expired, the transaction is automatically blocked. You can configure up to 6 different ID check configurations. A single product/department should only be assigned 1 ID check configuration.

Note the following points regarding departments and PLUs:

* **Departments**- If you are setting up an ID Check for alcohol, each department in which alcohol can be sold must have the parameter for ID Check selected.
* **PLUs**- If you are setting up an ID Check for cigarettes, each PLU that is a cigarette product must have the parameter for ID Check selected.

{% hint style="info" %}
If a PLU does not have an ID check configured, but the PLU is part of a Department that has an ID check configured, you will get the ID check prompt if the PLU is added.
{% endhint %}

*After a less restrictive item is added to a transaction, for example an item that requires just entering the DOB, and then if an item with more restriction that requires input from user/cashier/customer in addition to the DOB is added to the transaction, the item will not be allowed to be added to the transaction. An error appears “Purchase Not Allowed.”*

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

*From software release 55.00, more information is asked if needed.*

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

{% hint style="info" %}
*Some of the features are available only in Verifone Commander Release 52.09 or higher.*
{% endhint %}

<table><thead><tr><th valign="top">Field/Button</th><th valign="top">Allowable Value/Function</th></tr></thead><tbody><tr><td valign="top">Customer ID Check Name</td><td valign="top">Enter the name for the ID check. The name usually includes a description of the product being checked (alphanumeric - up to 16 characters).</td></tr><tr><td valign="top">Age</td><td valign="top">Enter the minimum age of the customer who can purchase the item (1 - 99).</td></tr><tr><td valign="top">Bypass ID Check</td><td valign="top"><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Available only in Commander Release 52.09 or higher.</p></div><p>Enable this parameter to skip the ID check and confirm that the customer is allowed to purchase the item. If Confirm is not selected at the prompt, the item is not added to the transaction.</p><ul><li>Security Level: Enter the security level of the cashier or manager who can skip the ID check to confirm that the customer is legally allowed to purchase the item.</li><li>Confirmation Prompt: Enter the confirmation prompt shown to cashier to accept that the customer is allowed to buy the item.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><em>This feature is mutually exclusive from the Force Scan/Swipe feature.</em></p></div></td></tr><tr><td valign="top">Force Scan/Swipe Only</td><td valign="top"><p>When “Force Scan/Swipe Only” parameter is enabled, cashier is not allowed to enter the details manually.</p><ul><li><p>Perform ID Legitimacy Check: Bar code scanner or magnetic stripe reader captures at least two pieces of personal information from the ID card’s bar code/ magnetic stripe and temporarily display them to the clerk on the POS screen.</p><ul><li>Piece of personal information #1: ID card full name.</li><li>Piece of personal information #2: License Number.</li></ul></li></ul><p>The retail associate compares the information displayed on the POS screen to the information on the physical ID and approves the transaction if there is no mismatch between ID bar code/magnetic stripe and physical ID text or declines the transaction if there is mismatch between ID bar code/magnetic stripe and physical ID text.</p><p><em>This setting is not used/needed when using TruAge.</em></p><ul><li>Manual Entry Override: When selected, an employee with a high enough security level can manually enter ID details even though “Force Scan/Swipe Only” is selected.</li><li>Security Level: Security level of the employee who can perform a manual entry override.</li></ul><p><em>A bar code scanner or the magnetic strip reader captures birthdate information from the ID card’s bar code or magnetic stripe and performs an automated mathematical check to ensure that the consumer meets the minimum age requirement to approve the transaction.</em></p><p><em>If the consumer is below the minimum age requirement, the transaction does not complete.</em></p></td></tr><tr><td valign="top">Exceptions</td><td valign="top"><p>The Date-Based and Military exceptions are disabled (grayed out) when the site is onboarded to use TruAge.</p><ul><li>Military Exception: After manual entry of the DOB from the ID, if the DOB fails standard minimum age limit check, but, passes military minimum age limit test, a prompt appears asking if it is a military ID.</li><li>Date Based or Grandfather Exception: Grandfather age check is based on a past minimum age requirement. If the DOB check meets this secondary date-based exception, the transaction can be completed.</li></ul></td></tr><tr><td valign="top">Delete</td><td valign="top">Click to delete the selected ID check.</td></tr></tbody></table>


---

# 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/age-restriction/configuring-age-restriction.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.
