> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/services/quick-pay.md).

# Quick Pay

**Quick Pay** allows staff to process payment more efficiently by adding quick payment buttons directly to the order creation screen. This allows instant payment selection without opening the full payment window.

This can be enabled or disabled **per service**. 

> Even when Quick Pay is enabled, users can go to the "Checkout" screen and take all standard actions.

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2FdtRNXoS3mfqNLDKGeJSr%2Fimage.png?alt=media&amp;token=5d673343-6e9b-4b03-a851-1f5e5e6fbb28" alt=""><figcaption></figcaption></figure>

## How to Enable Quick Pay

1. In the [**Admin Portal**](https://admin.gobossit.com/), navigate to **Channels > Services**.
2. Select relevant **service** then go to **Config** tab.
3. Enable **Allow quick payment in order flow** option.
4. Click **Save**.

{% hint style="info" %}

#### Auto complete order on quick payment

This enables auto-complete for orders processed via Quick Pay.
{% 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.bossithq.com/services/quick-pay.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.