> For the complete documentation index, see [llms.txt](https://useepay.gitbook.io/useepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://useepay.gitbook.io/useepay/ji-shu-fu-wu.md).

# 技术服务

1.Q：什么是重复订单号？

A：同一终端号，同一网址下，该笔交易的订单号已经在支付系统中存有成功或待处理记录， 就不允许再次提交付款。

2.Q：安全性警告是指什么？

 中文：

![](/files/Psf4G2znkGTDVFwge6nD)

英文：

![](/files/QzraqErntGhlgxMf0OF6)

A：这是个别浏览器，如火狐(FireFox)等针对一些数据返回的安全性提示框。是因为数据

从一个安全加密页面到另一个非安全页面的警报，如果商户的订单页面是一个安全加密的页面，则不会出现这提示。

如果点击了继续(Continue)，数据会继续返回到网站中；如果点击了取消(Cancel)，数据则不会返回到网站中，订单状态有可能不会改变。

3\. Q：UseePay的支付页面是否支持移动端？是否支持多语种？

A：UseePay的支付页面是支持移动端的支付方式，支持 5种语言；移

4\. Q：UseePay的支付系统是否支持APP？

A：UseePay的支付系统可支持 Android 和 iOS 两个版本的 SDK，详细可联系UseePay技术支持人员。

5\. Q：UseePay的交易数据能保久？ A： 交 易 数 据 会 被 永 久 保 存  。43.Q：UseePay的支付系统支持开源系统？是否有 API 文档？

A：目前支持Zencart、Magento、Opencart、Prestashop、Ecshop、shopEx 等开源电商系统支付插件。所有支付方式都有 API 文档，API 文档分中文版和英文版，详细可联系UseePay技术支持人员。

6.Q：UseePay有哪些支付页面模式？

A：UseePay目前的支付页面模式分跳转和内嵌两种，详细可联系UseePay技术支持人员。


---

# 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://useepay.gitbook.io/useepay/ji-shu-fu-wu.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.