> For the complete documentation index, see [llms.txt](https://whitepaper.wicrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.wicrypt.com/4.-tokenomics/4.4-payments.md).

# 4.4 Payments

$WNT tokens is used as a default form of payments and interactions in Wicrypt network (although ecosystem participants can choose settling transaction in one of the applicable stablecoins as well).

Choosing $WNT will always remain a more profitable means of payment due to lower provisions on host <-> customer transactions and discounts on hubs/NFTs prices. Please refer to the table below for more details:

![Stablecoin vs $WNT based settlement
](/files/Jrw7klapxTNYDMwMKrHW)

Any host determining prices for their services and choosing $WNT as a settlement method will be protected by the potential negative impact of token volatility by the so-called ‘dynamic pricing system’ in which the service price is pegged to the stablecoin value but it’s still expressed in $WNT as a unit.

Subsequently, the price of the service is being regularly updated through Wicrypt oracle using multiple source feeds to prevent any potential exploits. Additionally, price is being double checked upon purchase transaction execution.


---

# 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://whitepaper.wicrypt.com/4.-tokenomics/4.4-payments.md?ask=<question>&goal=<endgoal>
```

`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.