> For the complete documentation index, see [llms.txt](https://docs.tgshop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tgshop.io/uz/asosiy-sozlamalar/tolov-usullari/oz-tolov-usuli.md).

# O'z to'lov usuli

Ushbu yo'riqnoma do'kon uchun o'z to'lov usullarini sozlashga yordam beradi.

Onlayn to'lovlarni qabul qilishni xohlamasangiz yoki muqobil to'lov usullarini qo'shmoqchi bo'lsangiz — masalan, onlayn o'tkazma yoki naqd pul orqali — buni ushbu to'lov usuli orqali sozlash mumkin.

TGShop boshqaruv paneliga kiring, sozlamalarga o'ting va **«To'lov»** bo'limini tanlang.

So'ng **«O'z to'lov usulini qo'shish»** tugmasini bosing.

Paydo bo'lgan modal oynada maydonlarni to'ldiring.

1. **To'lov usuli nomi** — xaridor buyurtma rasmiylashtirish vaqtida ko'radigan to'lov usulining nomi.
2. **Chegirma turi** — chegirma turini ko'rsating (foizli yoki mutlaq).
3. **Chegirma miqdori** — chegirma miqdorini ko'rsating; bu parametr talab qilinmasa, maydonni bo'sh qoldiring.
4. **To'lov usulining tavsifi** — xaridor uchun to'lov usulining batafsil tavsifini kiriting; bu parametr talab qilinmasa, maydonni bo'sh qoldiring.

Saqlash va to'lov usulini yaratish uchun **«Ulash»** tugmasini bosing.


---

# 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.tgshop.io/uz/asosiy-sozlamalar/tolov-usullari/oz-tolov-usuli.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.