> For the complete documentation index, see [llms.txt](https://tgtaps.gitbook.io/tgtaps-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tgtaps.gitbook.io/tgtaps-docs/features/payments.md).
# Payments
## What can payments be used for?
You can accept payments for the:
* selling [rates](/tgtaps-docs/features/rates.md);
* selling access [to pages](/tgtaps-docs/features/pages/paid-pages.md);
* [selling points](/tgtaps-docs/features/payments/how-to-sell-points.md) (which can be spent on levels and upgrades).
For example, buying the page:
Buying points:
You can withdraw stars via your bot:
**Keep in mind:** withdrawal is allowed only after 21 days and starting from 1 000 stars.
You can view your payments in “Settings” → “Payments”.
## Where I can see payments?
You can see payments in two places:
* In bot “settings” → “Payments”. There are present all payments you have.
* In CRM -> Select user -> “Payments” and “Subscriptions”. There are present payments and subscriptions of the particular user.
## Subscriptions
Payments can be subscription. They withdraw money each month. If money were not withdrawn for more than 35 days - the subscription is canceled (rate returned, access to the page restricted, etc.).
Subscription can be cancelled in two ways:
* By user via block[ “Subscriptions list”](/tgtaps-docs/blocks/payments/subscriptions-list.md). It should be always placed in app with subscriptions or we may have to block your app until the problem is fixed.
* By admin in CRM (choose user -> go to section “subscriptions”).
***
Something unclear in docs or you know how to improve article? [Message us](https://t.me/tgtaps_support_bot) or [ask community](https://docs.tgtaps.com/tgtaps-docs/readme/community)! \
We will answer you and then promise to improve the article within 3 days.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://tgtaps.gitbook.io/tgtaps-docs/features/payments.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.