> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/cost-calculator-builder/payments/cash-payment.md).
# Cash Payment
You can let your customers pay in cash when they make an order with Cost Calculator. You can set up the cash payments in Global settings and individual settings of the calculator.
## Global Settings
To do this, go to **Global Settings** >**Payments**> **Cash Payment** and click **Apply to all calculators t**o apply settings to all calculators.
**Cash payment label** - The name of the field by clicking on your customers can pay in cash.
**Information to user** - You can put additional information such as address, location where your customers can pay you.
## Settings in the Calculator
You can also set up **Cash payment** in o the Cost Calculator in the **Payments** section of Individual settings. To do this, go to the **Settings** tab of the calculator you want and head over to the **Cash Payment** of the **Payments** section. There will be these settings:
After enabling Cash payment, you can see these settings:
**Cash payment label** - The name of the field by clicking on your customers can pay in cash.
**Information to user** - You can put additional information such as the address or location where your customers can pay you.
That's how it will look for your customers:
---
# 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.stylemixthemes.com/cost-calculator-builder/payments/cash-payment.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.
