Back to Details

gate-exchange-pay

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Resolving 
gate-cli
(binary path)

解析
gate-cli
（二进制文件路径）

Resolve 
gate-cli
 in order: (1) 
command -v gate-cli
 and 
gate-cli --version
 succeeds; (2) 
${HOME}/.local/bin/gate-cli
 if executable; (3) 
${HOME}/.openclaw/skills/bin/gate-cli
 if executable. Canonical rules: 
exchange-runtime-rules.md
 §4 (or 
gate-runtime-rules.md
 §4).
按以下顺序解析**
gate-cli
：(1)** 
command -v gate-cli
和
gate-cli --version
执行成功；(2) 若**
${HOME}/.local/bin/gate-cli
可执行则使用该路径；(3)** 若**
${HOME}/.openclaw/skills/bin/gate-cli
**可执行则使用该路径。标准规则：
exchange-runtime-rules.md
第4节（或
gate-runtime-rules.md
第4节）。

gate-exchange-pay — Gate Pay payment

gate-exchange-pay — Gate Pay支付

General Rules

通用规则

⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding. Do NOT select or call any tool until all rules are read. These rules have the highest priority. → Read gate-runtime-rules.md
  • Only use the 
    gate-cli
    commands explicitly listed in this skill.     Commands not documented here must NOT be run for these workflows, even if other interfaces expose them.
⚠️ 停止操作 — 在继续之前，您必须阅读并严格遵守共享运行时规则。在未阅读所有规则之前，请勿选择或调用任何工具。这些规则具有最高优先级。 → 阅读gate-runtime-rules.md
  • 仅使用本技能中明确列出的
    gate-cli
    命令    。即使其他接口提供了未在此处记录的命令，也不得在这些工作流中运行。

Scope and audience

适用范围与受众

This document is for end users and agents: in scenarios where payment is required first and the user has already chosen a payment method and selected Gate Pay, use this capability to complete the charge and output a receipt by calling Exchange MCP tool 
cex_pay_create_ai_order_pay
(no 
gate-cli
mapping in 
gate-cli/cmd/cex
; see 
MCP_LEGACY_TOOL_RESOLUTION.md
§二).
Before invoking this Skill, the user must have completed Gate account payment-related authorization. If not, guide them through Gate account authorization before charging.
本文档面向终端用户和Agent：在需要先付款且用户已选择支付方式为Gate Pay的场景中，通过调用Exchange MCP工具
cex_pay_create_ai_order_pay
（
gate-cli/cmd/cex
中无对应
gate-cli
映射；详见
MCP_LEGACY_TOOL_RESOLUTION.md
第二节）完成扣款并输出收据。
在调用本技能之前，用户必须完成Gate账户的支付相关授权。若未完成，需引导用户先完成Gate账户授权再进行扣款。

Language

语言要求

Use the user's language for receipts, pre-charge summaries, failures, and short confirmations. If the conversation mixes languages, follow the language of their payment or receipt request; keep one receipt in one language unless they switch.
收据、付款前摘要、失败提示和简短确认信息需使用用户的语言。若对话混合多种语言，遵循用户支付或收据请求所使用的语言；除非用户切换语言，否则一份收据仅使用一种语言。

When this applies

适用场景

  • The user has clearly expressed intent to pay (e.g. pay, confirm payment, checkout, pay for me).
  • Payment is required first (e.g. after HTTP 402 or an equivalent pay-first step when applicable), the user has selected Gate Pay as the payment method, and you are not substituting another channel.
  • All information required for the payment call is present and all required arguments for 
    cex_pay_create_ai_order_pay
    (no 
    gate-cli
    mapping in 
    gate-cli/cmd/cex
    ; see 
    MCP_LEGACY_TOOL_RESOLUTION.md
    §二) are satisfied (per MCP 
    inputSchema
    ); if anything is missing, complete it before paying.
  • This capability does not cover the first visit to a protected URL solely to obtain a 402; other parts of the conversation may handle that. Once the user has chosen Gate Pay and payment inputs are ready, use this capability to charge.
  • 用户已明确表达付款意图（如“付款”、“确认付款”、“结账”、“帮我付款”）。
  • 需要先付款（如HTTP 402或适用的等效先付款步骤），用户已选择Gate Pay作为支付方式，且您不会替换为其他渠道。
  • 付款调用所需的所有信息均已提供，且
    cex_pay_create_ai_order_pay
    的所有必填参数（
    gate-cli/cmd/cex
    中无对应
    gate-cli
    映射；详见
    MCP_LEGACY_TOOL_RESOLUTION.md
    第二节）均已满足（符合MCP 
    inputSchema
    ）；若有缺失，需在付款前补充完整。
  • 本技能不涵盖仅为获取402状态码而首次访问受保护URL的场景；对话的其他部分可能会处理该情况。一旦用户选择了Gate Pay且付款输入信息准备就绪，即可使用本技能进行扣款。

When this does not apply

不适用场景

  • The user only pastes large raw API text and payment inputs still cannot be determined reliably → do not charge; ask the user to complete details from the order or checkout page.
  • Finding merchants, comparing prices, or shopping guidance → out of scope.
  • Spot, contract, deposit, or on-chain transfers unrelated to charging a specific merchant order with Gate Pay → do not handle under this capability.
  • 用户仅粘贴大量原始API文本，仍无法可靠确定付款输入信息 → 请勿扣款；请用户从订单或结账页面补充完整详情。
  • 寻找商户、比价或购物指导 → 超出本技能范围。
  • 与使用Gate Pay支付特定商户订单无关的现货、合约、存款或链上转账 → 请勿通过本技能处理。

Domain Knowledge

领域知识

Gate Pay Overview

Gate Pay概述

Gate Pay is Gate's digital asset payment solution that enables users to pay for merchant orders using their Gate account balance. It supports pay-first flows (HTTP 402 protocol) where payment is required before accessing resources.
Gate Pay是Gate推出的数字资产支付解决方案，允许用户使用Gate账户余额支付商户订单。它支持先付款流程（HTTP 402协议），即访问资源前需先完成付款。

Authorization Requirements

授权要求

  • Users must complete Gate account payment authorization before any charge can be initiated
  • Authorization includes authentication and permission grants for payment-account debiting
  • If authorization is missing, expired, or invalid, guide users to complete Gate account authorization first
  • 用户必须在发起任何扣款前完成Gate账户支付授权
  • 授权包括身份验证和支付账户扣款权限授予
  • 若授权缺失、过期或无效，需引导用户先完成Gate账户支付授权

Payment Flow Constraints

支付流程约束

  • Payment is irreversible once successfully executed
  • Order information (order_id, amount, currency) must be complete before initiating payment
  • The skill only handles the charge step; resource fetching from merchants is out of scope
  • Payment voucher fields (if returned) may be used by downstream steps but should not be fabricated
  • 付款成功后不可撤销
  • 发起付款前必须确保订单信息（order_id、金额、币种）完整
  • 本技能仅处理扣款步骤；从商户获取资源超出本技能范围
  • 若返回付款凭证字段，可用于下游步骤，但不得伪造

Gate Pay vs Other Payment Methods

Gate Pay与其他支付方式的区别

  • This skill only handles Gate Pay payments; other payment methods (bank cards, other crypto wallets) are not in scope
  • Users must explicitly select Gate Pay as their payment method before this skill activates
  • 本技能仅处理Gate Pay付款；其他支付方式（银行卡、其他加密钱包）不在范围内
  • 用户必须明确选择Gate Pay作为支付方式后，本技能才会激活

gate-cli command index

gate-cli命令索引

Tool namePurposeType
cex_pay_create_ai_order_pay
(no 
gate-cli
mapping in 
gate-cli/cmd/cex
; see 
MCP_LEGACY_TOOL_RESOLUTION.md
§二)		Debit the user's Gate Pay payment account for a merchant orderWrite
工具名称用途类型
cex_pay_create_ai_order_pay
（
gate-cli/cmd/cex
中无对应
gate-cli
映射；详见
MCP_LEGACY_TOOL_RESOLUTION.md
第二节）		从用户的Gate Pay支付账户中扣除商户订单款项写入

Authentication

身份验证

  • Interactive file setup: when 
    GATE_API_KEY
     and 
    GATE_API_SECRET
     are not both set on the host, run 
    gate-cli config init
     to complete the wizard for API key, secret, profiles, and defaults (see gate-cli).
  • Env / flags: 
    gate-cli config init
     is not required when credentials are already supplied — e.g. both 
    GATE_API_KEY
     and 
    GATE_API_SECRET
     set on the host, or 
    --api-key
     / 
    --api-secret
     where supported — never ask the user to paste secrets into chat.
  • API Key Required: Yes
  • Additional Authorization Required: Yes, Gate Pay payment authorization must already be completed
  • Note: This skill executes a private payment action through authenticated Exchange MCP tooling. Payment authorization is required in addition to the runtime's API-key-backed execution capability.
Note: If there is no order-status query tool available and the user only asks whether they paid, explain the limitation; do not charge again as a substitute for querying.
  • 交互式文件设置：当主机上未同时设置**
    GATE_API_KEY
    和
    GATE_API_SECRET
    时，运行
    gate-cli config init
    **完成API密钥、密钥、配置文件和默认设置的向导流程（详见gate-cli）。
  • 环境变量/标志：当凭证已提供时，无需运行**
    gate-cli config init
    ** —— 例如主机上已同时设置**
    GATE_API_KEY
    和
    GATE_API_SECRET
    ，或在支持的情况下使用
    --api-key
    ** / 
    --api-secret
     —— 切勿要求用户在聊天中粘贴密钥。
  • 需要API密钥：是
  • 需要额外授权：是，必须已完成Gate Pay支付授权
  • 注意：本技能通过经过身份验证的Exchange MCP工具执行私密支付操作。除运行时基于API密钥的执行能力外，还需支付授权。
注意：若没有订单状态查询工具，且用户仅询问是否已付款，请说明此限制；请勿通过再次扣款来替代查询。

Installation Check

安装检查

  • Required: 
    gate-cli
    when using CLI-backed flows (run 
    sh ./setup.sh
    from this skill directory if missing; optional 
    GATE_CLI_SETUP_MODE=release
    ).
  • Add 
    $HOME/.openclaw/skills/bin
    to 
    PATH
     if you invoke 
    gate-cli
    by name (or the directory where 
    setup.sh
     installs it).
  • Credentials: When 
    GATE_API_KEY
     and 
    GATE_API_SECRET
     are both set (non-empty) for the host, do not require 
    gate-cli config init
    . When both are unset or empty, remind the operator to run 
    gate-cli config init
     or to configure 
    GATE_API_KEY
     / 
    GATE_API_SECRET
     in the matching skill from the skill library (never ask the user to paste secrets into chat).
  • Sanity check: Confirm the runtime and payment preconditions before executing charges; use 
    gate-cli --version
     or deployment-specific checks as appropriate.
  • 必填项：使用基于CLI的工作流时需要
    gate-cli
    （若缺失，可从本技能目录运行
    sh ./setup.sh
    ；可选设置
    GATE_CLI_SETUP_MODE=release
    ）。
  • 若通过名称调用
    gate-cli
    ，需将
    $HOME/.openclaw/skills/bin
    添加到**
    PATH
    **（或
    setup.sh
    安装
    gate-cli
    的目录）。
  • 凭证：当主机上的**
    GATE_API_KEY
    和
    GATE_API_SECRET
    均已设置（非空）时，无需要求运行
    gate-cli config init
    。当两者均未设置或为空时，提醒操作员运行
    gate-cli config init
    ** 或从技能库中匹配的技能配置**
    GATE_API_KEY
    ** / 
    GATE_API_SECRET
    （切勿要求用户在聊天中粘贴密钥）。
  • 完整性检查：执行扣款前确认运行时和付款前置条件；根据情况使用**
    gate-cli --version
    **或特定部署的检查方式。

Execution mode

执行模式

Read and strictly follow 
references/gate-cli.md
, then execute this skill's Gate Pay charge workflow.
  • SKILL.md
    keeps payment intent routing, product boundaries, and user-facing policy.
  • references/gate-cli.md
    is the authoritative 
    gate-cli
    execution contract for charge inputs, confirmation gates, and failure fallback.
阅读并严格遵守
references/gate-cli.md
，然后执行本技能的Gate Pay扣款工作流。
  • SKILL.md
    记录付款意图路由、产品边界和面向用户的策略。
  • references/gate-cli.md
    是
    gate-cli
    执行扣款输入、确认关卡和失败回退的权威约定。

Workflow

工作流

Step 0: Verify Payment Readiness

步骤0：验证付款就绪状态

Action: Validate that all preconditions are met before proceeding.
Key data to extract:
  • User has selected Gate Pay as payment method
  • All required payment parameters are present: 
    order_id
    , 
    amount
    , 
    currency
  • User has completed Gate payment authorization (if not, halt and guide authorization)
Decision: If any required input is missing → ask user to provide complete details. If authorization is incomplete → guide authorization flow. Otherwise proceed to Step 1.
操作：继续之前验证所有前置条件是否满足。
需提取的关键数据：
  • 用户已选择Gate Pay作为支付方式
  • 所有必填付款参数均已提供：
    order_id
    、金额、币种
  • 用户已完成Gate支付授权（若未完成，暂停并引导授权）
决策：若任何必填输入缺失 → 请用户提供完整详情。若授权未完成 → 引导授权流程。否则进入步骤1。

Step 1: Confirm User Payment Intent

步骤1：确认用户付款意图

Action: Ensure user clearly intends to execute payment.
Key data to extract:
  • User expresses payment intent (e.g., "pay", "confirm payment", "checkout", "pay for me")
  • User has not declined or cancelled the payment
Decision: If user intent is unclear or negative → do not proceed with payment. If intent is clear → proceed to Step 2.
操作：确保用户明确有意执行付款。
需提取的关键数据：
  • 用户表达付款意图（如“付款”、“确认付款”、“结账”、“帮我付款”）
  • 用户未拒绝或取消付款
决策：若用户意图不明确或为否定 → 请勿继续付款。若意图明确 → 进入步骤2。

Step 2: Present Payment Details (Optional)

步骤2：展示付款详情（可选）

Action: Display key charge details for user verification. This is informational and does not require an explicit forced confirmation step. It does not replace Step 1: calling the payment tool still requires the clear payment intent established there (see Safety Rules).
Key data to extract:
  • Merchant order ID
  • Amount and currency
  • Payment method (Gate Pay)
Output format:
Planned charge
Merchant order ID: {order_id}
Amount due: {amount} {currency}
Payment method: Gate Pay
Decision: Proceed to Step 3 after displaying details when Step 1's payment-intent gate is satisfied; the optional display is for transparency only.
操作：显示关键扣款详情供用户验证。此步骤仅为告知性，无需强制用户明确确认。但这不能替代步骤1：调用付款工具仍需步骤1中确立的明确付款意图（详见安全规则）。
需提取的关键数据：
  • 商户订单ID
  • 金额和币种
  • 支付方式（Gate Pay）
输出格式：
计划扣款
商户订单ID: {order_id}
应付金额: {amount} {currency}
支付方式: Gate Pay
决策：当步骤1的付款意图关卡满足后，展示详情即可进入步骤3；可选展示仅为提高透明度。

Step 3: Execute Payment

步骤3：执行付款

Action: Call Exchange MCP tool 
cex_pay_create_ai_order_pay
(no 
gate-cli
mapping in 
gate-cli/cmd/cex
; see 
MCP_LEGACY_TOOL_RESOLUTION.md
§二) with validated parameters.
Call 
cex_pay_create_ai_order_pay
(no 
gate-cli
mapping in 
gate-cli/cmd/cex
; see 
MCP_LEGACY_TOOL_RESOLUTION.md
§二) with:
  • order_id
    : Merchant order identifier
  • amount
    : Payment amount
  • currency
    : Payment currency
  • Other required fields per MCP 
    inputSchema
Key data to extract:
  • Payment status (success/failure)
  • Transaction timestamp
  • Payment confirmation details (order_id, amount, status)
  • Voucher fields (if applicable, e.g., prepayId) for downstream use
Decision: If payment succeeds → proceed to Step 4 with success receipt. If payment fails → proceed to Step 4 with failure handling.
操作：使用已验证的参数调用Exchange MCP工具
cex_pay_create_ai_order_pay
（
gate-cli/cmd/cex
中无对应
gate-cli
映射；详见
MCP_LEGACY_TOOL_RESOLUTION.md
第二节）。
调用
cex_pay_create_ai_order_pay
（
gate-cli/cmd/cex
中无对应
gate-cli
映射；详见
MCP_LEGACY_TOOL_RESOLUTION.md
第二节）时需传入：
  • order_id
    ：商户订单标识符
  • amount
    ：付款金额
  • currency
    ：付款币种
  • MCP 
    inputSchema
    要求的其他必填字段
需提取的关键数据：
  • 付款状态（成功/失败）
  • 交易时间戳
  • 付款确认详情（order_id、金额、状态）
  • 凭证字段（如适用，例如prepayId）供下游使用
决策：若付款成功 → 进入步骤4并输出成功收据。若付款失败 → 进入步骤4并处理失败情况。

Step 4: Output Result

步骤4：输出结果

Action: Report payment result to user in their language (per Language section).
Success path: Output receipt using Report Template format (see Report Template section).
Failure path: Provide user-friendly error explanation without exposing internal error codes or stack traces (see Error Handling section).
操作：使用用户的语言（详见语言部分）向用户报告付款结果。
成功路径：使用报告模板格式输出收据（详见报告模板部分）。
失败路径：提供用户友好的错误说明，不得暴露内部错误代码或堆栈跟踪（详见错误处理部分）。

Judgment Logic Summary

判断逻辑摘要

ConditionStatusMeaning
Payment inputs complete + user selected Gate Pay + user intent clear + authorization validExecuteProceed with payment execution via 
cex_pay_create_ai_order_pay
(no 
gate-cli
mapping in 
gate-cli/cmd/cex
; see 
MCP_LEGACY_TOOL_RESOLUTION.md
§二)
Missing order_id, amount, or currencyBlockAsk user to provide complete payment details from merchant order page
User has not selected Gate PayBlockThis skill does not apply; other payment methods are out of scope
User intent unclear or user declinesBlockDo not initiate payment; wait for clear confirmation or handle cancellation
Authorization missing, expired, or invalidBlockGuide user to complete Gate account payment authorization first
User only asks payment status (no query tool available)InformExplain limitation; do not charge again to infer status
Payment API returns successReportOutput success receipt with transaction details (localized)
Payment API returns failureReportOutput failure explanation in user's language with actionable guidance
条件状态含义
付款输入完整 + 用户选择Gate Pay + 用户意图明确 + 授权有效执行通过
cex_pay_create_ai_order_pay
（
gate-cli/cmd/cex
中无对应
gate-cli
映射；详见
MCP_LEGACY_TOOL_RESOLUTION.md
第二节）执行付款
缺失order_id、金额或币种阻止请用户从商户订单页面提供完整付款详情
用户未选择Gate Pay阻止本技能不适用；其他支付方式超出范围
用户意图不明确或用户拒绝阻止请勿发起付款；等待明确确认或处理取消请求
授权缺失、过期或无效阻止引导用户先完成Gate账户支付授权
用户仅询问付款状态（无查询工具可用）告知说明限制；请勿通过再次扣款推断状态
付款API返回成功报告输出包含交易详情的成功收据（本地化）
付款API返回失败报告使用用户的语言输出失败说明及可行指导

Report Template

报告模板

Success Receipt

成功收据

Use field labels in the user's language (see Language section). Template shape (English labels shown as reference):
✅ Payment Success

Merchant order ID: {order_id}
Amount paid: {amount} {currency}
Payment status: {status_text_matching_payment_result}
Payment time: {timestamp; include timezone or follow product rules}
Payment method: Gate Pay

⚠️ Important: Digital asset transactions are generally irreversible. Please verify the transaction details above.
Voucher handling: If the successful payment response includes voucher-style fields (final names per spec, e.g., prepayId), downstream steps may use them to fetch resources from the merchant. This skill does not fetch resources; voucher fields should be preserved for external use if applicable.
使用用户语言的字段标签（详见语言部分）。模板格式（英文标签仅作参考）：
✅ 付款成功

商户订单ID: {order_id}
支付金额: {amount} {currency}
付款状态: {status_text_matching_payment_result}
付款时间: {timestamp; 包含时区或遵循产品规则}
支付方式: Gate Pay

⚠️ 重要提示：数字资产交易通常不可撤销。请核实上述交易详情。
凭证处理：若成功付款响应包含凭证类字段（最终名称以规范为准，例如prepayId），下游步骤可使用这些字段从商户获取资源。本技能不负责获取资源；若适用，需保留凭证字段供外部使用。

Failure Explanation

失败说明

Use the user's language (see Language section). Provide specific, actionable guidance based on error type:
Template:
❌ Payment Failed

Reason: {user_friendly_explanation}
Suggested action: {actionable_next_step}
Do not: Expose internal error codes, stack traces, or raw API responses to the user.
使用用户的语言（详见语言部分）。根据错误类型提供具体、可行的指导：
模板：
❌ 付款失败

原因: {user_friendly_explanation}
建议操作: {actionable_next_step}
禁止：向用户暴露内部错误代码、堆栈跟踪或原始API响应。

Runtime rules

运行时规则

Before calling any payment-related tools, follow the Agent and MCP usage rules shipped with this product, and comply with exchange-runtime-rules.md.
在调用任何付款相关工具之前，请遵循随产品提供的Agent和MCP使用规则，并遵守exchange-runtime-rules.md。

Scenarios

场景示例

Reviewer-oriented scenario templates (happy path, errors, localization, and safety edges) live in 
references/scenarios.md
in this skill directory. Use that file for parity checks against this SKILL; do not treat the path as a Skills Hub hyperlink.
面向审核人员的场景模板（正常流程、错误、本地化和安全边界）位于本技能目录的
references/scenarios.md
中。请使用该文件与本SKILL进行一致性检查；请勿将该路径视为技能中心的超链接。

Error Handling

错误处理

Error TypeConditionUser Message (Template)Recommended Action
Insufficient balancePayment API returns balance insufficient error"Payment failed: Your Gate Pay balance is insufficient for this payment. Please top up your account and try again."Guide user to deposit funds or use alternative payment method
Authorization expired/invalidAPI indicates authorization is missing, expired, or invalid"Payment failed: Your Gate payment authorization has expired or is invalid. Please complete Gate account authorization again."Guide user through Gate account payment authorization flow
Order not foundAPI indicates order_id does not exist or cannot be found"Payment failed: The order ID is invalid or no longer valid. Please verify the order details with the merchant and try again."Ask user to obtain valid order information from merchant
Order expiredAPI indicates order has expired or payment window closed"Payment failed: This order has expired and can no longer be paid. Please place a new order with the merchant."Suggest user to create new order or contact merchant for replacement
Duplicate paymentBusiness logic detects duplicate charge attempt for same order"This order has already been paid. Please check your payment history or contact support if you believe this is incorrect."Do not initiate duplicate charge; explain limitation
Invalid parametersMissing required fields or invalid format"Payment cannot be processed: Some required information is missing or invalid. Please provide complete order details (order ID, amount, currency)."Ask user to provide complete and valid payment parameters
Network/system errorAPI timeout, connection failure, or unspecified system error"Payment failed due to a temporary system issue. Please try again in a few moments or contact support if the problem persists."Suggest retry later; do not expose technical error details
General rules:
  • Use the user's language for all error messages (see Language section)
  • Do not expose internal error codes, stack traces, or raw API responses
  • Provide actionable next steps for each error type
  • If error type is unclear, provide neutral guidance to retry or contact support
错误类型条件用户消息（模板）推荐操作
余额不足付款API返回余额不足错误"付款失败：您的Gate Pay余额不足以完成本次付款。请充值后重试。"引导用户充值或使用其他支付方式
授权过期/无效API显示授权缺失、过期或无效"付款失败：您的Gate支付授权已过期或无效。请重新完成Gate账户授权。"引导用户完成Gate账户支付授权流程
订单未找到API显示order_id不存在或无法找到"付款失败：订单ID无效或已失效。请与商户核实订单详情后重试。"请用户从商户获取有效订单信息
订单过期API显示订单已过期或付款窗口已关闭"付款失败：该订单已过期，无法继续付款。请向商户重新下单。"建议用户创建新订单或联系商户更换订单
重复付款业务逻辑检测到同一订单存在重复扣款尝试"该订单已完成付款。请查看您的付款记录，若有疑问请联系客服。"请勿发起重复扣款；说明限制
参数无效缺失必填字段或格式无效"无法处理付款：部分必填信息缺失或无效。请提供完整订单详情（订单ID、金额、币种）。"请用户提供完整且有效的付款参数
网络/系统错误API超时、连接失败或未指定系统错误"因临时系统问题导致付款失败。请稍后重试，若问题持续请联系客服。"建议稍后重试；不得暴露技术错误详情
通用规则：
  • 所有错误消息使用用户的语言（详见语言部分）
  • 不得暴露内部错误代码、堆栈跟踪或原始API响应
  • 为每种错误类型提供可行的下一步操作
  • 若错误类型不明确，提供中立指导，建议重试或联系客服

Data Privacy & Collection

数据隐私与收集

This skill processes user payment data through the Gate MCP. All data is transmitted directly to the Gate API for payment execution.
Data handling statement:
  • Data collection: This skill collects order information (order ID, amount, currency) and user payment authorization credentials as required for payment execution
  • Data storage: No user data is stored locally by this skill. All payment transactions are processed and recorded by Gate's secure payment infrastructure
  • Data transmission: Payment data is transmitted exclusively to Gate API endpoints. No third-party services are involved
  • Data protection: All data transmission uses encrypted channels compliant with Gate's security standards
  • User control: Users can view their payment history through Gate's official platform. Transaction records are maintained per Gate's data retention policy
Age restriction: This skill is intended for users aged 18 or above with full civil capacity, consistent with Gate's platform requirements.
本技能通过Gate MCP处理用户付款数据。所有数据直接传输至Gate API以执行付款。
数据处理声明：
  • 数据收集：本技能收集订单信息（订单ID、金额、币种）和用户支付授权凭证，以满足付款执行需求
  • 数据存储：本技能不会在本地存储任何用户数据。所有付款交易均由Gate的安全支付基础设施处理和记录
  • 数据传输：付款数据仅传输至Gate API端点。不涉及任何第三方服务
  • 数据保护：所有数据传输使用符合Gate安全标准的加密通道
  • 用户控制权：用户可通过Gate官方平台查看付款历史。交易记录将根据Gate的数据保留政策保存
年龄限制：本技能面向年满18周岁且具备完全民事行为能力的用户，符合Gate平台要求。

Risk Disclaimers

风险声明

⚠️ Important notices for Gate Pay users:
  1. Risk of loss: Paying with digital assets involves financial risk; you may lose the amounts debited if the order or merchant context is wrong. Verify every detail before authorizing a charge.
  2. Transaction irreversibility: Digital asset transactions are generally irreversible. Once a Gate Pay payment is successfully executed, it cannot be undone. Please carefully verify all order details (merchant, amount, currency) before confirming payment.
  3. Not investment advice: This skill provides payment execution functionality only. Any payment decisions are the user's sole responsibility. This does not constitute investment, financial, tax, or legal advice.
  4. Regulatory compliance: Users must ensure their use of Gate Pay complies with applicable laws and regulations in their jurisdiction. Gate operates under licenses in multiple jurisdictions. Users are responsible for understanding and complying with local payment and digital asset regulations.
  5. Merchant responsibility: Gate Pay facilitates payment to third-party merchants. Gate is not responsible for merchant products, services, delivery, refunds, or disputes. Users should verify merchant legitimacy before making payments.
  6. AI output disclaimer: AI-assisted payment processing is for convenience only and does not constitute any representation, warranty, or guarantee by Gate regarding payment success, merchant reliability, or transaction outcomes.
⚠️ Gate Pay用户重要提示：
  1. 损失风险：使用数字资产付款存在财务风险；若订单或商户信息有误，您可能会损失扣除的金额。授权扣款前请核实所有详情。
  2. 交易不可撤销：数字资产交易通常不可撤销。Gate Pay付款成功后无法撤销。确认付款前请仔细核实所有订单详情（商户、金额、币种）。
  3. 非投资建议：本技能仅提供付款执行功能。任何付款决策由用户自行负责。本技能不构成投资、财务、税务或法律建议。
  4. 合规要求：用户必须确保使用Gate Pay符合所在司法管辖区的适用法律法规。Gate在多个司法管辖区持有牌照。用户有责任了解并遵守当地支付和数字资产法规。
  5. 商户责任：Gate Pay仅为向第三方商户付款提供便利。Gate不对商户的产品、服务、交付、退款或纠纷负责。付款前请核实商户合法性。
  6. AI输出声明：AI辅助付款处理仅为方便使用，Gate不对付款成功、商户可靠性或交易结果作出任何陈述、保证或担保。

Safety Rules

安全规则

Confirmation Requirements

确认要求

This skill follows a streamlined confirmation model for payment execution:
  1. User intent confirmation: The user must clearly express payment intent (e.g., "pay", "confirm payment", "checkout")
  2. Parameter verification: Payment details (order ID, amount, currency) may be displayed for user verification, but no additional forced confirmation step is required beyond clear payment intent
  3. Single-use confirmation: Each payment intent is single-use. If parameters or merchant details change, re-confirm intent is required
  4. No execution without intent: Without clear user payment intent, the skill operates in query/information mode only
本技能遵循简化的付款执行确认模型：
  1. 用户意图确认：用户必须明确表达付款意图（如“付款”、“确认付款”、“结账”）
  2. 参数验证：可展示付款详情（订单ID、金额、币种）供用户验证，但除明确付款意图外无需额外强制确认步骤
  3. 单次意图确认：每个付款意图仅可使用一次。若参数或商户信息变更，需重新确认意图
  4. 无意图不执行：若无明确用户付款意图，本技能仅处于查询/信息模式

Authorization Guards

授权防护

  • Pre-execution check: Before calling 
    cex_pay_create_ai_order_pay
    (no 
    gate-cli
    mapping in 
    gate-cli/cmd/cex
    ; see 
    MCP_LEGACY_TOOL_RESOLUTION.md
    §二), verify user has completed Gate payment authorization
  • Authorization validation: If authorization is missing, expired, or invalid, halt payment and guide user through authorization flow
  • No bypass: Payment execution must not bypass authorization requirements under any circumstances
  • 执行前检查：调用
    cex_pay_create_ai_order_pay
    （
    gate-cli/cmd/cex
    中无对应
    gate-cli
    映射；详见
    MCP_LEGACY_TOOL_RESOLUTION.md
    第二节）前，验证用户已完成Gate支付授权
  • 授权验证：若授权缺失、过期或无效，暂停付款并引导用户完成授权流程
  • 禁止绕过：任何情况下均不得绕过授权要求执行付款

Duplicate Payment Prevention

重复付款预防

  • Transaction tracking: Do not charge the same order_id twice within a conversation context
  • Status query limitation: If user asks "did I pay?", explain query limitation rather than initiating a duplicate charge to infer status
  • 交易跟踪：在对话上下文内不得对同一order_id进行两次扣款
  • 状态查询限制：若用户询问“我付款了吗？”，请说明查询限制，而非通过发起重复扣款来推断状态

Security Requirements

安全要求

  1. Do not fabricate order information, payment status, timestamps, or payment vouchers.
  2. Do not initiate a charge when inputs are incomplete or the user did not select Gate Pay for this payment.
  3. If the charge did not succeed, do not output a success receipt or claim payment succeeded.
  4. Do not charge twice for the same business transaction.
  5. Do not invent voucher fields that the payment API did not return.
  6. Do not expose sensitive data (API keys, internal error codes, system architecture details) in user-facing messages.
  7. Validate all input parameters before calling payment API to prevent injection or malformed data attacks.
  1. 不得伪造订单信息、付款状态、时间戳或付款凭证。
  2. 若输入信息不完整或用户未选择Gate Pay作为本次支付方式，请勿发起扣款。
  3. 若扣款未成功，不得输出成功收据或声称付款已成功。
  4. 不得对同一业务交易进行两次扣款。
  5. 不得编造付款API未返回的凭证字段。
  6. 不得在面向用户的消息中暴露敏感数据（API密钥、内部错误代码、系统架构详情）。
  7. 调用付款API前验证所有输入参数，防止注入或格式错误攻击。",