> 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/how-terminus-works.md).

# How Terminus Works

Terminus abstracts a complex transaction into a simple payment experience. Behind a single scan-to-pay action sits a multi-layer process that interprets local payment intent, routes user-funded digital assets through integrated channels, and completes merchant settlement in local fiat.

## Step 1: QR Recognition and Payment Parsing

The payment begins when a user scans an existing merchant QR code. Terminus reads the information encoded in that QR payload and interprets the merchant destination, transaction amount, or associated payment data according to the local payment rail format.

This allows the product to interact with the commercial environment already in use, rather than requiring merchants to display a new crypto-specific code.

## Step 2: User Payment Authorization

Once the payment is parsed, the user sees the payment details inside Terminus and confirms the transaction using a supported digital asset. This is the point where consumer intent is translated into an executable payment instruction.

The product should make this step clear and controlled:

* what is being paid,
* what asset is funding the payment,
* what the estimated outcome is,
* and when the user is committing to the action.

## Step 3: Payment Channel and Routing

After user confirmation, Terminus routes the payment through its integrated channel stack. Partners such as `AEON` operate here as embedded payment infrastructure rather than as separate user-facing destinations.

This distinction matters. The user pays through Terminus. Integrated channels support execution, conversion, and flow completion beneath the interface.

## Step 4: Conversion and Settlement Orchestration

Once the crypto-funded leg of the payment is initiated, Terminus coordinates the transaction path required to deliver value into the local payment system. This includes quoting, routing, conversion logic, and settlement orchestration so that the merchant receives value in the expected fiat format.

This is the heart of the product:

* crypto funds the payment,
* local rails complete the merchant-facing side,
* and Terminus acts as the orchestrator between those environments.

## Step 5: Reconciliation and Exception Handling

A payment product becomes infrastructure only when it handles the imperfect edge cases of the real world. Terminus therefore needs clear systems for:

* payment confirmation,
* state tracking,
* failure handling,
* refund or reversal policies where applicable,
* and reconciliation across the transaction stack.

These mechanisms are critical for trust, especially in offline commerce environments where payment clarity is essential.

```mermaid
flowchart LR
    A["User Scans Local QR"] --> B["Terminus Parses Payment Intent"]
    B --> C["User Confirms Crypto Payment"]
    C --> D["Terminus Routes Through Integrated Channels"]
    D --> E["Conversion and Settlement Orchestration"]
    E --> F["Local QR Rail Settlement"]
    F --> G["Merchant Receives Local Fiat"]
    E --> H["Reconciliation and Risk Controls"]
```

## Why This Matters

The significance of the Terminus model is not merely that a crypto payment can happen. It is that the transaction can complete across systems without forcing either user or merchant into awkward new behavior.

That is what makes the flow commercially meaningful and scalable.


---

# 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/how-terminus-works.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.