> 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/market-thesis/why-terminus.md). # Why Terminus Terminus is built around a practical question: how can crypto be spent in the real world without asking merchants to become crypto-native? Its answer is to invert the usual design logic of crypto payments. Rather than rebuilding merchant behavior around blockchain infrastructure, Terminus rebuilds blockchain access around merchant reality. ## The Core Promise The Terminus promise can be expressed in one sentence: `Spend any crypto, settle in local fiat, change nothing for the merchant.` That promise is powerful because it aligns with the incentives of both sides of the transaction. For the user: * the payment starts with digital assets they already hold, * it avoids unnecessary manual off-ramping, * and it turns crypto balances into something useful in everyday life. For the merchant: * the payment still lands as local currency, * the merchant keeps existing QR rails, * and the transaction does not introduce crypto volatility or operational burden. ## Invisible Off-Ramp Terminus is best understood as an invisible off-ramp payment system. The user can fund a purchase with crypto, but the complexity of conversion, routing, and settlement is handled in the background. This is different from simply offering an off-ramp service. A standalone off-ramp asks the user to exit crypto first and spend later. Terminus compresses the conversion and spending processes into a single commerce event. That is what makes the product viable in real time. ## Built for Existing Merchant Reality Many payment startups underestimate how difficult merchant behavior is to change. Terminus treats that as a design constraint, not a sales obstacle. Merchants already have habits, systems, and trust structures around local QR payment infrastructure. Terminus does not try to replace those habits. It works through them. This creates several forms of leverage: * faster merchant compatibility, * lower education burden, * fewer integration demands, * and stronger scalability across fragmented local markets. ## The Right Product at the Right Abstraction Layer A strong Web3 payment product cannot live only at the wallet layer or only at the rail layer. It has to sit between user intent and merchant settlement. That is where Terminus operates: * close enough to the user to deliver a simple scan-to-pay experience, * close enough to the settlement layer to move value into local fiat rails, * and modular enough to connect with payment channels, liquidity providers, wallets, and ecosystem partners. This positioning gives Terminus an advantage over products that are too consumer-light to drive adoption or too infrastructure-heavy to own user demand. ## A Product With Network Potential Terminus starts with the narrow problem of making offline crypto spending work. But the architecture naturally leads toward a broader outcome: a payment network that coordinates consumers, merchants, rails, channels, and ecosystem incentives across multiple Southeast Asian markets. That is why the project is larger than a feature or a single app. It is a system for making crypto economically useful in the environments where people already spend money every day. --- # 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/market-thesis/why-terminus.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.