> 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/user-experience.md).

# User Experience

The success of a payment product is determined less by its underlying architecture than by how little the user needs to think about that architecture while paying.

Terminus is built around that principle. The goal is not to remind users they are performing a complex crypto-to-fiat orchestration. The goal is to make the payment feel direct, legible, and fast.

## A Familiar Flow

The ideal Terminus interaction feels structurally familiar:

1. scan the merchant's QR code,
2. review the payment details,
3. confirm the asset and amount,
4. complete the payment,
5. receive confirmation.

This matters because the user is not being asked to learn a crypto-native ritual. They are following a recognizable mobile payment path, with digital assets funding the transaction behind the scenes.

## No Manual Off-Ramp

One of the biggest points of friction in crypto spending is the mental and operational overhead of converting before purchase. A user often has to think through where to off-ramp, how much to convert, what fees they will pay, and whether they have prepared the right local balance in advance.

Terminus removes that preparation step. By embedding conversion and settlement into the payment flow, the product lets the user act on immediate intent. That is essential for offline commerce, where a payment decision is made in seconds.

## No App-Hopping

The user should not need to jump across multiple apps to complete a single purchase. Terminus is designed as the primary user interaction surface. Integrated payment channels operate underneath the experience instead of forcing the user to navigate external flows for each transaction.

This is a subtle but important product advantage. Every extra app transition reduces completion rates and makes a daily-use product feel unreliable.

## Built for Confidence

A Web3 payment product only becomes habit-forming if users trust the result. That means the product must communicate clearly:

* how much is being paid,
* what asset is being used,
* when the payment is complete,
* and what happens if there is an exception or delay.

Clarity is especially important in cross-system payments where the user is funding a local commercial action with a digital asset.

## Everyday Spending, Not Just Demo Usage

The user experience should not optimize only for first-time novelty. It should optimize for repetition.

That means Terminus must be good enough for:

* small, frequent payments,
* casual use in convenience retail,
* spontaneous travel spending,
* and regular use where a consumer wants crypto to function as a live balance rather than a distant reserve.

When the product reaches that threshold, it stops being a Web3 curiosity and becomes part of payment behavior.


---

# 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/user-experience.md?ask=<question>&goal=<endgoal>
```

`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.