> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/guides/payments/customize-payments/collect-tips-donations-at-the-checkout.md).
# Collect tips/donations at the checkout
You can collect tips or donations in your store by enabling a specific section at the last checkout step:
To do so, simply send a PUT request with the JSON-formatted body. There, define the \`tipsSettings\` object with all the settings inside.
Request example:
`PUT` `https://app.ecwid.com/api/v3/{storeId}/profile`
```json
{
"tipsSettings": {
"enabled": true, // must be `true`
"type": "PERCENT", // `PERCENT` or `ABSOLUTE`
"options": [
0,
5,
10
],
"defaultOption": 10,
"title": "Support us with a donation",
"subtitle": "We appreciate all donations, and even the tiniest bit helps us continue what we’re doing."
}
}
```
You can specify one of the donation types:
* `PERCENT` to collect tips tied to the order total, for example, 10% extra tip
* `ABSOLUTE` to collect tips unrelated to the order total, for example, $15
The `options` array and the `defaultOption` are predefined values for the tip, and the `title` and \`subtitle\` fields describe why customers should leave a tip.
In response you’ll see \`200 OK\` HTTP status with the response body:
```json
{
"updateCount": 1
}
```
Which means that you’ve successfully enabled tips at the checkout.
---
# 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.ecwid.com/guides/payments/customize-payments/collect-tips-donations-at-the-checkout.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.
