> 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/veloce-pos/veloce/electronic-funds-transfer-eft/veloce-mobile-application/payment-terminal-setup/payfacto-payment-application.md).

# PayFacto Payment Application

## PayFacto Payment Application

PayFacto payment terminals are typically shipped to the merchants with the necessary applications pre-installed and pre-configured.

For more information on the PayFacto Payment application, please review the associated online documentation:

 

[PayFacto Payment Application Quick Reference Guide](https://documentation.payfacto.com/PF_Payment/QRG/CA-EN/index.htm)

[PayFacto - Payment (standalone mode) User Guide](https://desk.payfacto.com/portal/en/kb/articles/payfacto-user-guide-1-4-2021)

 

If you need further assistance to download, install or configure the PayFacto Payment application, please contact PayFacto technical support.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payfacto.com/payfacto-knowledge/veloce-pos/veloce/electronic-funds-transfer-eft/veloce-mobile-application/payment-terminal-setup/payfacto-payment-application.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.