> 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/canada-doc-center/terminals/countertop/pax-a80/accessories/introduction.md).
# Introduction
### Introduction
This guide will explain how to install the cable attachment bracket for the PAX A80 terminal (part number AZP-310006) designed to prevent the accidental disconnection of cables from the terminal.
{% hint style="warning" %}
IMPORTANT! This cable attachment bracket is only for use with PAX A80 terminals used in countertop environments. It is not compatible with the A80 extension pole for drive-through applications.
{% endhint %}
The topics covered in this guide include:
* [Preparing the Terminal](https://documentation.payfacto.com//Accessories/A80_Cable_Attachment/CA-EN/First_Topic.htm#PrepareTerminal)
* [Installing the T Bracket](https://documentation.payfacto.com//Accessories/A80_Cable_Attachment/CA-EN/Installing_the_T_Bracket.htm)
* [Cable Installation](https://documentation.payfacto.com//Accessories/A80_Cable_Attachment/CA-EN/Cable_Installation.htm)
***
### Preparing the Terminal
Before you can install the cable attachment to the PAX A80 terminal, you must prepare the terminal by doing the following:
1. Power off the terminal by pressing and holding the red X key on the physical keypad.
\
2. Turn the terminal over and remove all cables from the terminal's communication ports.
\
---
# 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/canada-doc-center/terminals/countertop/pax-a80/accessories/introduction.md?ask=&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.