> For the complete documentation index, see [llms.txt](https://docs.onta.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onta.network/basics/images-and-media/product-overview.md).
# Product Overview
### What is Onta Network?
Onta Network is committed to providing a comprehensive, regulation-compliant payment solution for users, merchants, and projects. By leveraging the existing Web2 payment rails alongside the unique advantages of blockchain—decentralization, efficiency, low cost, security, and scalability—Onta Network builds a new generation of payment infrastructure.The goal is to seamlessly bridge the transactional demands of Web2 with the assets and users, enabling true interoperability and accelerating the real-world adoption of crypto payments.
### How does it work?
Onta Network streamlines the Web3 payment experience by integrating multiple players into a seamless transaction loop, balancing Web2 compatibility with Web3-native architecture. The process involves five key participants: the Customer, Merchant, Onta Network, Acquirer, and OTC Service Provider.
The complete payment flow unfolds as follows：
1. **Payment Initiation**\
The customer initiates a purchase at a merchant’s checkout point and selects the option to pay with crypto. The merchant enters the transaction amount and generates a dynamic QR code via the Onta Network terminal.
2. **Wallet Selection and Authorization**\
The customer scans the QR code using their smartphone, which launches a browser-based checkout page showing the merchant name, payment amount, and supported wallet options (e.g., MetaMask, Trust Wallet). The customer selects their preferred wallet, completes KYC if required, and authorizes the transaction in their wallet interface.
3. **Transaction Settlement**\
Onta Network receives the crypto payment from the user’s wallet and notifies the acquirer in real time. Simultaneously, Onta Network transfers the received assets to a partnered OTC service provider, which converts the crypto to fiat and settles the amount with the acquirer on a T+1 basis.
4. **Confirmation and Completion**\
Once the acquirer is updated, both the merchant and customer are notified of the payment success. The merchant prints the receipt, and the transaction is completed.
This modular design ensures that Web3 users can pay directly from their wallets, while Web2 merchants receive fiat without needing to interact with crypto infrastructure. To make this payment experience as smooth and seamless as its Web2 counterparts, significant architectural considerations are required.
\
---
# 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.onta.network/basics/images-and-media/product-overview.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.
