> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/bang-zhu-zhong-xin/re-men-fen-lei/zhi-fu/huilshi-yong-shuo-ming.md).

# 汇率使用说明

### 一、Atlas 汇率使用原则

Atlas 在订单的出票报价、退票退款及相关金额结算中，统一采用**实时汇率**进行币种换算和金额处理。

实时汇率，是指系统在订单报价、退款、差额结算或其他金额结算节点，根据对应业务处理时点可用的汇率进行币种换算。由于汇率会随市场、支付渠道或结算渠道变化而波动，不同业务处理时点适用的汇率可能存在差异。

因此，订单报价将按报价时点的实时汇率折算；后续如发生退款、差额结算或其他金额处理，也将按对应处理时点的实时汇率折算。为保持全流程汇率口径一致，Atlas 不会在部分环节使用实时汇率，而在其他结算环节改用固定汇率或锁定汇率。

### 二、关于汇率波动对金额的影响

同一订单在报价、退款或其他结算环节中的折算金额，可能会受到汇率波动影响。

报价与支付属于同一交易确认流程，客户在当前报价下完成支付时，Atlas 将以报价展示金额作为客户应付金额。报价至支付期间如因短时间汇率波动产生汇差，该部分汇差风险由 Atlas 承担，不会再向客户调整支付金额。

退款、差额结算等属于后续的独立金额处理场景，相关金额将根据实际处理时点的实时汇率进行折算。由此产生的金额差异属于实时汇率机制下的正常结果，不代表订单金额、退款规则或 Atlas 服务费用发生了变化。

### 三、补充说明

固定汇率或锁定汇率，通常指在报价阶段提前约定某一汇率，并在约定范围内保持不变。Atlas 暂不支持使用固定汇率或锁定汇率进行订单报价、支付、退款及相关金额结算。

原始预订交易与后续退款（或结算）交易之间的汇率可能出现波动，由此产生的任何损益，Atlas 概不承担任何责任。

如个别业务场景存在特殊结算安排，将以 Atlas 与客户双方正式确认的规则为准。


---

# 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://resources.atriptech.com/bang-zhu-zhong-xin/re-men-fen-lei/zhi-fu/huilshi-yong-shuo-ming.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.