> For the complete documentation index, see [llms.txt](https://terminus-1.gitbook.io/terminus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://terminus-1.gitbook.io/terminus-docs/product-and-infrastructure/product-overview.md). # Product Overview Terminus is the user-facing layer of the network. It is the product through which consumers bring digital assets into offline commerce. The experience is intentionally simple: a user encounters a merchant QR code, opens Terminus, pays with supported crypto, and the merchant continues to receive local fiat. ## A Consumer Product With Infrastructure Underneath The product experience is straightforward because Terminus sits on top of a deeper infrastructure stack. Users do not need to see the routing, quoting, settlement, and channel integrations that make the payment possible. They only need confidence that the transaction will work. This balance between simplicity on the surface and orchestration underneath is central to the Terminus design. ## Scan Existing Fiat QR Codes Terminus is not asking merchants to display new crypto-specific payment interfaces. It works by reading and interpreting the same local fiat QR codes merchants already use in day-to-day business. That matters because it aligns the product with the existing commercial environment. The product becomes useful immediately in places where QR payment is already normal. ## Pay With Supported Digital Assets The payment is funded by supported digital assets. Over time, this can include stablecoins and major liquid crypto assets, with the exact asset set governed by operational, liquidity, and compliance considerations. The user does not need to manually convert into local fiat before making the payment. The conversion and settlement logic happens in the background as part of the payment flow itself. ## Merchant Receives Local Currency Merchants are not expected to take custody of crypto. They are not asked to manage wallet exposure or asset volatility. The payment lands in terms compatible with the existing local settlement system. This preserves merchant trust and makes the product scalable in mainstream commerce environments. ## The Right User Experience for Adoption A product designed for daily spending must feel close to existing payment behavior. That is why Terminus aims for a user experience defined by: * low cognitive overhead, * minimal steps, * fast confirmation, * and clear transaction outcomes. In effect, Terminus turns a crypto-funded payment into a QR commerce experience that feels native in a mobile-first market. --- # 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://terminus-1.gitbook.io/terminus-docs/product-and-infrastructure/product-overview.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.