> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/uk-and-intl/terminals/countertop/pax-a80/a80-setup-guide/terminal-activation/overview.md).

# Overview

## Terminal Activation

PayFacto uses a self-service terminal activation procedure designed to save time while also providing better security. The new activation procedure applies only to countertop and mobile PAX payment terminals using the Android operating system. The new procedure applies to:

* All new merchants activating their terminals for the first time
* Any existing merchants adding new payment terminals
* Any existing merchants receiving replacement terminals

***

### Overview

After you configure the terminal's network connection(s) and power on the terminal, the procedure comprises of 2 parts:

* [Activate the terminal with a One Time Passcode (OTP)](broken://pages/gkcRKuy2xY4pla9iH5t3#activate-terminal)
* [Set the Administrator and Merchant passwords](broken://pages/RvngxYiQxxyYL9gYOEeR#set-passwords)

{% hint style="info" %}
NOTE: If you have multiple new payment terminals, you need to perform the activation procedure on each terminal individually.
{% endhint %}


---

# 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.payfacto.com/payfacto-knowledge/uk-and-intl/terminals/countertop/pax-a80/a80-setup-guide/terminal-activation/overview.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.