> 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/merchant-experience.md). # Merchant Experience Merchants are central to payment adoption, but they are not obligated to care about crypto. This is one of the foundational assumptions behind Terminus. A payment product designed for real-world scale must minimize the amount of change it asks from merchants. The winning path is not to convert merchants into crypto operators. It is to preserve the tools, workflows, and settlement logic they already trust. ## Keep Existing Payment Behavior The merchant experience with Terminus is intentionally conservative. Merchants continue to use their existing QR payment setup and continue to think in local fiat terms. They do not need to adopt new point-of-sale hardware or learn on-chain asset management. This matters because merchant acceptance is usually constrained by operational burden, not conceptual opposition. If the new payment method increases complexity, it becomes a hard sell. If it fits invisibly into existing workflows, it becomes economically legible. ## No Crypto Exposure A merchant accepting payments through Terminus is not expected to hold or manage digital assets. They do not need to monitor volatility, custody balances, or train staff to handle blockchain-specific edge cases. The merchant promise is simple: * keep the current QR-based collection logic, * receive local fiat, * and avoid direct crypto complexity. This reduces the emotional and operational risk of adoption and makes the product easier to scale across mainstream commercial environments. ## No New Hardware or Operational Rebuild Retail merchants care about throughput, consistency, and low disruption. Terminus respects that reality by avoiding requirements for new hardware, major software change, or payment-specific retraining. This is especially important in dense offline commerce categories where transactions are fast, margins are thin, and owner attention is limited. A system that forces process change will struggle. A system that leaves existing behavior intact can spread more naturally. ## Better Demand Without Merchant Reinvention From the merchant perspective, the ideal outcome is not to become a crypto merchant. It is to gain access to more paying customers without changing how the business operates. Terminus supports that outcome by translating crypto-funded consumer demand into standard merchant settlement behavior. This creates a new source of demand while preserving the merchant's existing financial logic. ## Merchant Adoption as a Function of Low Friction Merchant growth does not need to begin with explicit crypto enthusiasm. It can begin with convenience and continuity. That is why the merchant experience is one of Terminus's strongest structural advantages. If users can bring crypto into payments while merchants continue acting as they always have, network expansion becomes much more realistic. --- # 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/merchant-experience.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.