> 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/using-age-restriction/truage-online-age-verification.md).

# TruAge Online Age Verification

When the feature is turned on, the cashier or the customers do not notice any difference in the way the transactions are processed from the above scenarios other than when the following happen:

* the number of items allowed to be purchased by a customer have exceeded the limit.
* the cashier tries to suspend a transaction that has online verified items.

If online verification is turned on, first the system level verifications are performed before the transactions are sent for online verification.

If any age restricted item is present in the transaction, suspend transaction is not allowed.

## If the Site is Onboarded with TrueAge

* All the items are by default enabled for online verification.
* If the Item is configured for Force Scan, then the item can be scanned with valid Mobile QR code or Physical ID.
* If the customer token from the Mobile QR code is already used, then "ALREADY USED TOKEN" message is shown to the cashier. The customer needs to generate a new QR code to scan.
* If item is configured for manual ID check and the customer doesn't want to scan the QR code or Physical ID, then the cashier can enter the DOB manually to allow the sale to continue if it meets the minimum age locally. The transaction is sent to TrueAge with Age Verify Token = none.

## If the Site is Not Onboarded with TrueAge

The cashier should ask for a DOB/DL and not accept a mobile QR code scan since the items cannot be sent to TrueAge.

## If Customer is not Onboarded with TrueAge Mobile App

Customer needs to present their physical ID for scanning. If they do not have the ID, the DOB should be entered manually if the item is configured for manual entry.

## Error When Exceeding Limit

<figure><img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/KpLTQTidMUPGAODf2ple/Unknown%20image" alt=""><figcaption></figcaption></figure>

The number in the bracket is the number of items that has exceeded the limit.

## Error When Suspending Transaction

When online age verification is turned on and after age restricted items are added to a transaction, the transaction cannot be suspended.

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

## TruAge Offline Transactions

If Verifone Commander cannot communicate with the TruAge servers, the encrypted ID checks are saved offline. A maximum of 5000 offline transactions can be stored.

Offline encrypted ID checks are sent to the auditing server when the connection is established.

An alarm line message appears on the POS indicating that the TruAge Verification is offline.

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

## Auto Upgade and Offline Transactions

Before an [Auto Upgrade](https://commanderhelp.verifone.com/feature-references/features-and-products-references/auto-upgrade.md), any outstanding offline TruAge transactions will be logged in the Journal and Tlog before the upgrade. After the transactions are logged in the Tlog and Journal, they will be removed from the system and will no longer be forwarded to the TruAge server.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/fBdomAA0JgsOcXyo517V/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/age-restriction/using-age-restriction/truage-online-age-verification.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.
