> 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/complete_accessible_keypad.md).

# complete\_accessible\_keypad

{% columns %}
{% column width="33%" %}
![](https://414590445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yCod23DpRJz8E6kZwmN%2Fuploads%2Fgit-blob-d77444fdedc5533997c52f9e308f841961ede10b%2Faccessibility_complete_keypad.png?alt=media)
{% endcolumn %}

{% column %}
**Description**

Informs the customer that the payment is completed successfully. Prompts the customer to remove the card if it is still inserted. The terminal can be configured to either play a single beep or to continuously play beeps until the card is removed. If in accessibility mode, there will also be a voice prompt for card removal.

\
**Merchant/Customer action**

The customer needs to remove the card. The screen will not time out as long as the card remains inserted.

\
**Audio Instructions**

“Payment complete. Please remove card.”

\
**Configuration Parameters**

`Navigator.DefaultVolumeLevel` - Minimum audio instructions volume level

`Terminal.ContinuousBeep` - Defines if the device should play a single beep or periodic beep (every second), when prompting to remove a chip card.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/functional-specification/complete_accessible_keypad.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.
