> For the complete documentation index, see [llms.txt](https://axon-finance.gitbook.io/axon-finance-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://axon-finance.gitbook.io/axon-finance-docs/part-iv-payfi-yin-qing/part4-payfi.md).

# 引读：四场景层层叠加价值

> 一条支付 rail 打底，四个场景层层叠加价值。

Part III 建好了地基。本部分展示地基之上生长出的业务：**PayFi 的四大场景**。

这四个场景不是并列的四个功能，而是一个**层层叠加的价值结构**——底层是结算 rail，它承载一切；在其上叠加货币市场，捕获时间价值；再叠加跨境与商户场景，触达实体商业；而 AI 代理支付（Part V）则贯穿其中，成为机器时代的支付方式。

```mermaid
flowchart TB
    S["① 稳定币即时结算 Rail<br/>地基场景，承载一切"] --> M["② PayFi 货币市场<br/>捕获货币的时间价值"]
    S --> X["③ 跨境 B2B 与商户收单<br/>触达实体商业"]
    M --> V["超额收益来源"]
    X --> V
    M --> C["④ 美股带单引擎<br/>首个落地旗舰产品"]
    style S fill:#f5541c,stroke:#0a0908,color:#fff
    style M fill:#ff8a3d,stroke:#0a0908,color:#0a0908
    style X fill:#ff8a3d,stroke:#0a0908,color:#0a0908
    style C fill:#f5541c,stroke:#0a0908,color:#fff
```

本部分的章节地图：

* **4.1** 稳定币即时结算 Rail —— 承载一切的地基场景。
* **4.2** PayFi 货币市场 —— 浮存金与链上信贷，PayFi 的超额收益来源。
* **4.3** 跨境 B2B 与商户收单 —— 让 PayFi 触达实体商业。
* **4.4** 货币时间价值的金融学 —— 支撑这一切的金融第一性原理。
* **4.5** 美股带单引擎 —— 把上述能力兑现成产品的首个 PayFi 旗舰落地。


---

# 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://axon-finance.gitbook.io/axon-finance-docs/part-iv-payfi-yin-qing/part4-payfi.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.