> 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/support-uk/ux700/how-tos/how-to-use-accessible-pin-entry.md).

# How To Use Accessible PIN Entry

Enter a PIN independently as a blind or visually impaired customer on the UX700 terminal.

{% hint style="info" %}
**Use this when** a blind or visually impaired customer needs to enter their PIN themselves, without disclosing it to the merchant.
{% endhint %}

{% hint style="warning" %}
**Do NOT use this when** the customer wants magnification, colour contrast, and audio feedback on a visible keypad instead — see How To Use Assistant PIN Entry.
{% endhint %}

This page explains how a customer uses Accessible PIN Entry mode on the UX700. It requires accessibility to be enabled in the device configuration.

## Enter the PIN accessibly

{% stepper %}
{% step %}

### Enter Accessible PIN Entry mode

On the card prompt, double-tap anywhere on the screen. The PIN entry screen will appear blank. The total amount is vocalised, along with an instruction on how to present a card ("Please present your card").
{% endstep %}

{% step %}

### Navigate the keypad

Drag a finger across the screen to navigate the 12-pad keypad (10 digits, OK, and Cancel). Audio feedback plays each time you move to a different key.
{% endstep %}

{% step %}

### Confirm each digit

Double-tap anywhere on the terminal screen to confirm the key you last navigated to.
{% endstep %}

{% step %}

### Confirm the PIN

Once PIN entry is complete, navigate to the OK button (bottom right corner) and double-tap anywhere on the screen to confirm.
{% endstep %}

{% step %}

### Cancel if needed

To cancel at any point, navigate to the Cancel button (bottom left corner) and double-tap anywhere on the display to exit PIN entry.
{% endstep %}
{% endstepper %}

## Guidelines

* Audio feedback reports whether a PIN entered was correct or incorrect.
* After two unsuccessful PIN entries, a short training exercise starts automatically — see How To Use Accessibility Training.
* Exiting training cancels the ongoing transaction — a new transaction must be started to allow card and PIN entry again.

## FAQ

<details>

<summary>How does the customer know they're in Accessible PIN Entry mode?</summary>

The total amount and card presentation instruction are vocalised, and the PIN entry screen is blank.

</details>

<details>

<summary>What happens after two incorrect PIN entries?</summary>

The customer is guided through a short training exercise automatically — see How To Use Accessibility Training.

</details>

<details>

<summary>Keywords</summary>

Also called: accessible PIN, blind PIN entry. Search terms: double tap, PIN entry, card prompt, UX700.

</details>


---

# 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/support-uk/ux700/how-tos/how-to-use-accessible-pin-entry.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.
