> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/functional-specification/assistant_select_account_keypad.md).

# assistant\_select\_account\_keypad

{% columns %}
{% column width="33%" %}
![](/files/f0iBmaAef9CgGinDQqzI)
{% endcolumn %}

{% column %}
**Description**

If the card supports multiple accounts and the payment application was not able to determine the account by this point, the customer will be asked to select one of the accounts. Only the accounts that support the current transaction type will be presented to the customer. Note: For EMV cards where the account information can be derived from the Application Identifier (AID), the customer will never be prompted for account selection.

\
**Assistant mode gestures**

The list of options with increased button sizes and button text sizes will be presented with prefixed digits, starting with digit “1” for the first button, followed by “2” for the second button and so on. Upon pressing the corresponding digit on the hardware keypad, the selected list item will be processed. Audio for each option will be played for a long hold on the button or when dragging a finger across the button.

\
**Configuration Parameters**

`Navigator.AssistanceUserInterfaceTimeout` - Assistant mode inactivity timeout after which terminal present no activity warning timeout

`Navigator.DefaultVolumeLevel` - Minimum audio instructions volume level

\
**Audio Instructions**

“Please select account type.”
{% endcolumn %}
{% endcolumns %}

\---


---

# 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 dynamically by asking a question.

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

```
GET https://docs.verifone.com/functional-specification/assistant_select_account_keypad.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
