> For the complete documentation index, see [llms.txt](https://wp.verylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.verylabs.io/payment-innovation-and-vision.md).

# Payment Innovation & Vision

Very Network's Verychat is designed to be convenient and reliable, enabling anyone to easily set up a wallet and transact in cryptocurrencies with each other. Both offline and online merchants can receive payments from consumers without any network fees by using the QR code from the wallet within Verychat.

The maintenance of the Very Network is sustained not by transaction fees but by compensating nodes with VERY paid by advertisers. This allows validators to receive much higher rewards than transaction fees, enabling the network to maintain free transactions indefinitely.

This convenient, secure, and easy-to-install payment system, which is permanently free, will further maximize the number of Verychat users. Increased user engagement will, in turn, stimulate the demand for advertisers’ campaigns. As a result, the Very Network and Verychat ecosystem will become more robust and dedicated to serving numerous countries with inadequate financial infrastructure.


---

# 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:

```
GET https://wp.verylabs.io/payment-innovation-and-vision.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.