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

# host\_auth\_accessible

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

{% column %}
**Description**

Informs that the terminal is performing an online authorization by communicating with the host. If the terminal cannot connect to the host or a forced offline purchase is in progress, the transaction will be authorized offline, assuming that Store And Forward (SAF) is enabled and the transaction meets the SAF approval criteria.

See [Store And Forward (SAF)](broken://pages/t1loTZ4Sr38uqUbMEd0M)

\
**Audio Instructions**

“Authorizing, please wait.”

\
**Configuration Parameters**

`Navigator.DefaultVolumeLevel` - Minimum audio instructions volume level

\
**Error Scenarios**

If the customer removes the chip card, the transaction will be cancelled and a reversal will be generated.

If the terminal crashes or reboots while on this screen, when the payment application restarts or the terminal boots up, a power failure recovery will occur; the transaction will be declined and a reversal will be generated.
{% 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/host_auth_accessible.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.