> 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/web-app/order-creation/checkout/payment-options/configuring-payment-options-on-web-app.md).

# Configuring Payment Options on Web/App

{% hint style="danger" %}
**Reach out to your account manager before configuring payment options.**
{% endhint %}

You have the option to enable which payment methods are available on the web/app. This can be configured on a **service level**.

1. In the [**Admin Portal**](https://admin.gobossit.com/), go to the **group level**.
2. Navigate to **Website**
3. Under Services, click **Add service.**
4. Select the appropriate **service** from the dropdown and select:
   1. **Online —** for card payments
   2. **Online cash —** for cash payments
5. Click **Save**.

If you want to accept both cash and card payments, you need to add **two service entries**—one with Online payment method, the other with Online cash payment method.

> **For example:**
>
> You want to accept both cash and card payments for Delivery orders, while card payments only  for Collection orders.
>
> Your service entries should have:
>
> * Collection service - Online as payment method
> * Delivery service - Online as payment method
> * Delivery service - Online cash as payment method


---

# 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/web-app/order-creation/checkout/payment-options/configuring-payment-options-on-web-app.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.