> 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/applications/secure-payment/payment-standalone-mode/terminal-configuration/application-exit-password.md).

# Application Exit Password

### Application Exit Password

By default, the Secure Payment application's payment module requires the Merchant password before you can exit. You can choose whether or not to require the Merchant password, depending on your preference.

{% hint style="info" %}
NOTE: Be aware that if you disable this function, the Secure Payment application's payment module can be closed at any time by anyone, whether intended or not.
{% endhint %}

#### **To enable or disable the Merchant password before exiting:**

1. From the main screen, touch **Settings**.

\
![Settings button](https://documentation.payfacto.com/SecurePayment/Pay/UG/CA-EN/assets/images/Pay/MainSaleScreen_SettingsButton.png)

2. Enter the merchant password and touch **Confirm**.
3. Scroll to the **Configure application** section.
4. Touch **Terminal options**.
5. Scroll to the **General** section.
6. Enable the use of the Merchant password before closing the payment module by toggling the **Ask password on exit** switch to the right.
7. Disable the use of the Merchant password before closing the payment module by toggling the **Ask password on exit** switch to the left.
8. If you have more than one terminal, repeat steps **1** to **7** for each additional terminal where you want to set whether or not to use the Merchant password before exiting the application.


---

# 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/applications/secure-payment/payment-standalone-mode/terminal-configuration/application-exit-password.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.