Back to Details

uah-mono-payouts

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

UAH Mono Payouts

UAH Monobank提现服务

Use this skill when a user asks you to convert USDT BEP20 into a UAH payout through a verified exchange route.
MVP scope is narrow:
  • Source asset: USDT.
  • Source network: BEP20 / BNB Smart Chain.
  • Destination: UAH.
  • Contact source: agent-owned context, usually 
    ./mandate-wallet/contacts.csv
    .
  • Human approval: the user's explicit "create order" confirmation in chat. A separate web approval link is optional and not part of the default flow.
  • Status monitoring: poll the MCP order status every 60 seconds.
Do not use this skill for other tokens, other chains, portfolio management, generic wallet operations, or unrelated exchange flows.
当用户要求你通过经过验证的兑换渠道将USDT BEP20转换为UAH提现时，使用此技能。
MVP范围限定如下：
  • 源资产：USDT
  • 源网络：BEP20 / BNB Smart Chain
  • 目标货币：UAH
  • 联系人来源：Agent自有上下文，通常为
    ./mandate-wallet/contacts.csv
  • 人工审批：用户在聊天中明确确认“创建订单”。单独的网页审批链接为可选项，不属于默认流程
  • 状态监控：每60秒轮询一次MCP订单状态
请勿将此技能用于其他代币、其他链、投资组合管理、通用钱包操作或无关的兑换流程。

Prerequisites

前提条件

Installing this skill only installs these instructions. It does not guarantee that the payout MCP server is connected in the agent client.
MCP endpoint:
text
POST https://mcp-wallet.mandate.md/mcp
Use it as either:
  • a native remote HTTP MCP server when the agent client supports MCP servers, or
  • a direct HTTPS JSON-RPC endpoint when the agent has bash, curl, HTTP, browser automation, or another HTTP-capable tool.
Claude Code setup:
bash
claude mcp add --transport http uah-mono-payouts https://mcp-wallet.mandate.md/mcp
claude mcp list
Then restart Claude Code or run 
/mcp
and confirm the server is connected.
If a client says 
Native hook relay unavailable
, treat it as a client MCP bridge problem, not as proof that the hosted payout service is down. If you have any HTTP-capable tool, continue by calling the endpoint directly with JSON-RPC.
If native MCP tools are unavailable and you have no HTTP-capable tool, fail closed and tell the user:
text
The payout skill is installed, but this agent client cannot reach the payout MCP server: native MCP is unavailable and I do not have an HTTP-capable tool for direct JSON-RPC. I cannot quote, create an order, or provide deposit instructions safely.
安装此技能仅会安装这些指引，不保证Agent客户端已连接提现MCP服务器。
MCP端点：
text
POST https://mcp-wallet.mandate.md/mcp
可通过以下两种方式使用：
  • 当Agent客户端支持MCP服务器时，作为原生远程HTTP MCP服务器
  • 当Agent具备bash、curl、HTTP、浏览器自动化或其他HTTP能力工具时，作为直接HTTPS JSON-RPC端点
Claude Code设置：
bash
claude mcp add --transport http uah-mono-payouts https://mcp-wallet.mandate.md/mcp
claude mcp list
然后重启Claude Code或运行
/mcp
并确认服务器已连接。
如果客户端提示
Native hook relay unavailable
，将其视为客户端MCP桥接问题，而非托管提现服务已宕机的证明。如果您有任何HTTP能力工具，请继续通过JSON-RPC直接调用端点。
如果原生MCP工具不可用且无HTTP能力工具，则终止流程并告知用户：
text
提现技能已安装，但此Agent客户端无法连接到提现MCP服务器：原生MCP不可用，且我没有可用于直接JSON-RPC调用的HTTP工具。我无法安全地提供报价、创建订单或提供存款指引。

Mandatory Rules

强制规则

You must fail closed.
  • Never invent exchange rates, deposit addresses, comments, order IDs, expiry times, or support contacts.
  • Never scrape exchange or provider pages yourself.
  • Never tell the user to send funds before MCP returns 
    payment_instructions.can_send: true
    .
  • Never tell the user to send funds when the order expires in under 60 seconds.
  • Never continue if MCP is unavailable or order status is unclear.
  • Always show the network as 
    BEP20 / BNB Smart Chain
    , not just 
    USDT
    .
  • Always tell the user that each payment is subject to AML screening by the exchange/payment providers.
  • Always warn that wrong network, wrong amount, missing memo/comment, or reused expired orders can lose funds.
  • Always preserve the route label, order ID, order link, created time, expiry time, and support path returned by MCP. Do not replace them with guessed provider details.
  • Always show 
    exchanger_order_url
    when MCP returns it, including when it appears inside 
    payment_instructions.fields.exchanger_order_url
    .
  • For user-facing payment instructions, show the exchanger link as a Markdown link label, not as a raw technical URL.
  • Do not expose provider JSON/API status URLs as the user-facing order verification link. Use the human order page URL returned by MCP.
  • Always tell the user to verify the deposit address, exact amount, network, expiry, and provider status on the exchanger order page before sending.
  • If MCP returns deposit instructions without an exchanger verification link, say that the exchanger verification link was not returned. Do not invent one.
必须终止流程（Fail Closed）：
  • 切勿自行编造汇率、存款地址、备注、订单ID、过期时间或支持联系人
  • 切勿自行抓取交易所或服务商页面
  • 在MCP返回
    payment_instructions.can_send: true
    之前，切勿告知用户发送资金
  • 当订单剩余过期时间不足60秒时，切勿告知用户发送资金
  • 如果MCP不可用或订单状态不明，切勿继续流程
  • 始终显示网络为
    BEP20 / BNB Smart Chain
    ，而非仅显示
    USDT
  • 始终告知用户每笔支付均需经过交易所/支付服务商的AML筛查
  • 始终警告用户：错误的网络、错误的金额、缺失备注/留言或重复使用过期订单可能导致资金损失
  • 始终保留MCP返回的渠道标签、订单ID、订单链接、创建时间、过期时间和支持路径，切勿用猜测的服务商信息替换
  • 当MCP返回
    exchanger_order_url
    时，无论其是否出现在
    payment_instructions.fields.exchanger_order_url
    中，均需显示
  • 对于面向用户的支付指引，将交易所链接显示为Markdown链接标签，而非原始技术URL
  • 切勿将服务商JSON/API状态URL作为面向用户的订单验证链接，使用MCP返回的人工订单页面URL
  • 始终告知用户在发送资金前，需在交易所订单页面验证存款地址、精确金额、网络、过期时间和服务商状态
  • 如果MCP返回存款指引但未提供交易所验证链接，请告知用户未返回交易所验证链接，切勿自行编造

Mandatory Flow

强制流程

  1. Parse the user's payout intent.
  2. Resolve the recipient from your own context, usually 
    ./mandate-wallet/contacts.csv
    .
  3. If no contact matches, ask the user to add the recipient locally or provide exact Monobank UAH details.
  4. If multiple UAH accounts match, ask which account to use.
  5. If the UAH amount is ambiguous, ask whether the user means:
    • receive that UAH amount, or
    • send USDT worth that UAH amount.
  6. Build a 
    payout
    object with exact bank details.
  7. Call 
    quote_uah_payout
    .
  8. Present the best route briefly.
  9. Ask the user once whether to create the order if their prior message did not already say to proceed.
  10. Call 
    create_uah_payout_order
    .
  11. If the response includes 
    payment_instructions.can_send: true
    , show those exact payment instructions immediately, including the exchanger verification link if returned.
  12. If 
    payment_instructions.can_send
    is false or missing, do not send funds; show the returned blocker.
  13. Call 
    get_order_status
    every 60 seconds until the order reaches a final state. After payment is detected, MCP will notify the payout route when supported and then report the route-side provider status.
Final states:
  • completed
  • expired
  • rejected
  • failed
  • cancelled
If status becomes 
support_needed
, show the support details returned by MCP and stop automatic retries.
After the user sends funds, keep polling. Report these non-final states plainly:
  • deposit_seen
    : payment was detected on-chain; waiting for route-side confirmation.
  • payout_in_progress
    : payment was acknowledged; UAH payout is being processed.
  • support_needed
    : stop automatic retries and show MCP support details.
  1. 解析用户的提现意图
  2. 从自有上下文（通常为
    ./mandate-wallet/contacts.csv
    ）中解析收款人信息
  3. 如果无匹配联系人，请用户本地添加收款人或提供精确的Monobank UAH账户详情
  4. 如果有多个UAH账户匹配，请询问用户使用哪个账户
  5. 如果UAH金额不明确，请询问用户：
    • 是希望收到该UAH金额，还是
    • 发送价值该UAH金额的USDT
  6. 构建包含精确银行详情的
    payout
    对象
  7. 调用
    quote_uah_payout
  8. 简要展示最优渠道
  9. 如果用户之前的消息未明确表示继续，请询问用户是否创建订单
  10. 调用
    create_uah_payout_order
  11. 如果响应包含
    payment_instructions.can_send: true
    ，立即显示精确的支付指引，包括返回的交易所验证链接（如有）
  12. 如果
    payment_instructions.can_send
    为false或缺失，请勿发送资金，显示返回的阻塞信息
  13. 每60秒调用一次
    get_order_status
    ，直到订单进入最终状态。检测到支付后，MCP会在支持的情况下通知提现渠道，然后报告渠道端服务商状态
最终状态包括：
  • completed
    （已完成）
  • expired
    （已过期）
  • rejected
    （已拒绝）
  • failed
    （已失败）
  • cancelled
    （已取消）
如果状态变为
support_needed
，显示MCP返回的支持详情并停止自动重试
用户发送资金后，继续轮询。清晰报告以下非最终状态：
  • deposit_seen
    ：已在链上检测到支付；等待渠道端确认
  • payout_in_progress
    ：支付已确认；UAH提现正在处理中
  • support_needed
    ：停止自动重试并显示MCP支持详情

Contact Resolution

联系人解析

Contacts usually live in the agent's local project:
text
./mandate-wallet/contacts.csv
Supported UAH rails:
  • monobank_uah_card
  • monobank_uah_iban
For 
monobank_uah_card
, the contact must include a card number.
For 
monobank_uah_iban
, the contact must include IBAN, EDRPOU, and recipient full name.
Pass selected details to MCP as 
payout
. For a Monobank card:
json
{
  "rail": "monobank_uah_card",
  "currency": "UAH",
  "card_number": "4441111122223333",
  "recipient_full_name": "Swift Adviser",
  "telegram": "@SwiftAdviser",
  "email": "swiftadviser@gmail.com"
}
For a Monobank IBAN:
json
{
  "rail": "monobank_uah_iban",
  "currency": "UAH",
  "iban": "UA...",
  "edrpou": "12345678",
  "recipient_full_name": "Swift Adviser LLC",
  "telegram": "@SwiftAdviser",
  "email": "swiftadviser@gmail.com"
}
If the exchange flow asks for Telegram, use the contact Telegram if present. If missing and the flow requires a fallback, use:
text
@SwiftAdviser
If the exchange flow requires email and the contact has none, use:
text
swiftadviser@gmail.com
Do not invent bank details.
联系人通常存储在Agent的本地项目中：
text
./mandate-wallet/contacts.csv
支持的UAH渠道：
  • monobank_uah_card
    （Monobank UAH银行卡）
  • monobank_uah_iban
    （Monobank UAH IBAN账户）
对于
monobank_uah_card
，联系人必须包含卡号
对于
monobank_uah_iban
，联系人必须包含IBAN、EDRPOU和收款人全名
将选定的详情作为
payout
传递给MCP。对于Monobank银行卡：
json
{
  "rail": "monobank_uah_card",
  "currency": "UAH",
  "card_number": "4441111122223333",
  "recipient_full_name": "Swift Adviser",
  "telegram": "@SwiftAdviser",
  "email": "swiftadviser@gmail.com"
}
对于Monobank IBAN账户：
json
{
  "rail": "monobank_uah_iban",
  "currency": "UAH",
  "iban": "UA...",
  "edrpou": "12345678",
  "recipient_full_name": "Swift Adviser LLC",
  "telegram": "@SwiftAdviser",
  "email": "swiftadviser@gmail.com"
}
如果兑换流程需要Telegram信息，优先使用联系人的Telegram。如果缺失且流程需要备用信息，使用：
text
@SwiftAdviser
如果兑换流程需要邮箱信息且联系人无邮箱，使用：
text
swiftadviser@gmail.com
切勿编造银行详情

Amount Semantics

金额语义

Plain language like this is ambiguous:
text
переведи мне USDT в 5000 гривен
Ask one clarifying question:
text
5000 UAH should be the amount received, or should I send USDT worth about 5000 UAH?
If the user says they want to receive 5000 UAH, use:
json
{ "amount_semantics": "receive_fixed_uah" }
If the user says they want to send a 5000 UAH equivalent, use:
json
{ "amount_semantics": "send_uah_equivalent" }
For a request like:
text
выведи 500 usdt bep20 на mono uah
Treat 
500
as fixed USDT to send:
json
{
  "amount": "500",
  "amount_currency": "USDT",
  "amount_semantics": "send_uah_equivalent",
  "source_token": "USDT",
  "source_network": "BEP20"
}
如下类表述存在歧义：
text
переведи мне USDT в 5000 гривен
询问一个澄清问题：
text
5000 UAH 是您希望收到的金额，还是您希望发送价值约5000 UAH的USDT？
如果用户表示希望收到5000 UAH，使用：
json
{ "amount_semantics": "receive_fixed_uah" }
如果用户表示希望发送价值5000 UAH的USDT，使用：
json
{ "amount_semantics": "send_uah_equivalent" }
对于如下请求：
text
выведи 500 usdt bep20 на mono uah
将
500
视为固定发送的USDT金额：
json
{
  "amount": "500",
  "amount_currency": "USDT",
  "amount_semantics": "send_uah_equivalent",
  "source_token": "USDT",
  "source_network": "BEP20"
}

MCP Tools

MCP工具

Use the MCP server:
text
https://mcp-wallet.mandate.md/mcp
Expected tools:
  • contacts_search
  • quote_uah_payout
  • create_uah_payout_order
  • get_order_status
  • cancel_order
  • render_payment_instructions
  • check_usdt_bep20_balance
使用MCP服务器：
text
https://mcp-wallet.mandate.md/mcp
预期工具：
  • contacts_search
  • quote_uah_payout
  • create_uah_payout_order
  • get_order_status
  • cancel_order
  • render_payment_instructions
  • check_usdt_bep20_balance

Direct HTTPS JSON-RPC

直接HTTPS JSON-RPC

Use direct JSON-RPC when native MCP tools are unavailable but HTTP calls are possible. Every direct call is a 
POST
to:
text
https://mcp-wallet.mandate.md/mcp
List tools:
json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list",
  "params": {}
}
Call 
quote_uah_payout
:
json
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "quote_uah_payout",
    "arguments": {
      "payout": {
        "rail": "monobank_uah_card",
        "currency": "UAH",
        "card_number": "4441111122223333",
        "recipient_full_name": "Swift Adviser",
        "telegram": "@SwiftAdviser",
        "email": "swiftadviser@gmail.com"
      },
      "amount": "300",
      "amount_currency": "USDT",
      "amount_semantics": "send_uah_equivalent",
      "source_token": "USDT",
      "source_network": "BEP20"
    }
  }
}
Call 
create_uah_payout_order
:
json
{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "create_uah_payout_order",
    "arguments": {
      "quote_id": "quote-id-returned-by-quote_uah_payout",
      "payout": {
        "rail": "monobank_uah_card",
        "currency": "UAH",
        "card_number": "4441111122223333",
        "recipient_full_name": "Swift Adviser",
        "telegram": "@SwiftAdviser",
        "email": "swiftadviser@gmail.com"
      },
      "user_timezone": "UTC"
    }
  }
}
Call 
get_order_status
:
json
{
  "jsonrpc": "2.0",
  "id": 4,
  "method": "tools/call",
  "params": {
    "name": "get_order_status",
    "arguments": {
      "order_id": "order-id-returned-by-create_uah_payout_order"
    }
  }
}
Read the tool result from the JSON-RPC 
result
field. If the response has 
error
, stop and report the structured blocker. Do not guess.
当原生MCP工具不可用但可进行HTTP调用时，使用直接JSON-RPC。每次直接调用均为
POST
请求至：
text
https://mcp-wallet.mandate.md/mcp
列出工具：
json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list",
  "params": {}
}
调用
quote_uah_payout
：
json
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "quote_uah_payout",
    "arguments": {
      "payout": {
        "rail": "monobank_uah_card",
        "currency": "UAH",
        "card_number": "4441111122223333",
        "recipient_full_name": "Swift Adviser",
        "telegram": "@SwiftAdviser",
        "email": "swiftadviser@gmail.com"
      },
      "amount": "300",
      "amount_currency": "USDT",
      "amount_semantics": "send_uah_equivalent",
      "source_token": "USDT",
      "source_network": "BEP20"
    }
  }
}
调用
create_uah_payout_order
：
json
{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "create_uah_payout_order",
    "arguments": {
      "quote_id": "quote-id-returned-by-quote_uah_payout",
      "payout": {
        "rail": "monobank_uah_card",
        "currency": "UAH",
        "card_number": "4441111122223333",
        "recipient_full_name": "Swift Adviser",
        "telegram": "@SwiftAdviser",
        "email": "swiftadviser@gmail.com"
      },
      "user_timezone": "UTC"
    }
  }
}
调用
get_order_status
：
json
{
  "jsonrpc": "2.0",
  "id": 4,
  "method": "tools/call",
  "params": {
    "name": "get_order_status",
    "arguments": {
      "order_id": "order-id-returned-by-create_uah_payout_order"
    }
  }
}
从JSON-RPC的
result
字段读取工具结果。如果响应包含
error
，停止流程并报告结构化阻塞信息，切勿猜测。

contacts_search

contacts_search

Optional compatibility helper for deployments that expose server-side demo contacts. Do not depend on it for the normal personal-agent flow.
If 
requires_disambiguation
is true, ask the user which account to use before quoting.
针对暴露服务器端演示联系人的部署的可选兼容性辅助工具。正常个人Agent流程请勿依赖此工具。
如果
requires_disambiguation
为true，在报价前询问用户使用哪个账户。

quote_uah_payout

quote_uah_payout

Use after payout details and amount semantics are known. Include the selected 
payout
object when available.
The backend ranks verified exchange options. You do not manually choose rates from websites.
Show one best route unless the user asks for alternatives.
If the response is:
json
{ "error": "quote_unavailable", "quotes": [] }
do not create an order and do not tell the user to send funds.
If 
diagnostics.supported_ranges
is present, use it to explain the supported send ranges for enabled routes. For 
reason: "amount_below_min"
, suggest the smallest 
min_send_amount
returned by MCP. For 
reason: "amount_above_max"
, suggest splitting the payout or using an amount at or below 
max_send_amount
. If 
supported_ranges
is empty, say that MCP currently has no enabled route for this method and amount.
Example:
text
No safe quote for 30 USDT.

This route is currently available from 230.41 to 10000 USDT. I did not create an order, and you should not send funds.
在提现详情和金额语义明确后使用。如有可用的选定
payout
对象，请包含在内。
后端会对经过验证的兑换选项进行排名，请勿手动从网站选择汇率。
除非用户要求查看其他选项，否则仅展示一个最优渠道。
如果响应为：
json
{ "error": "quote_unavailable", "quotes": [] }
请勿创建订单，也请勿告知用户发送资金。
如果存在
diagnostics.supported_ranges
，使用其说明可用渠道支持的发送金额范围。对于
reason: "amount_below_min"
，建议使用MCP返回的最小
min_send_amount
。对于
reason: "amount_above_max"
，建议拆分提现或使用等于或低于
max_send_amount
的金额。如果
supported_ranges
为空，请告知用户MCP当前没有适用于此方式和金额的可用渠道。
示例：
text
无法为30 USDT提供安全报价。

当前此渠道支持的发送金额范围为230.41至10000 USDT。我未创建订单，您请勿发送资金。

create_uah_payout_order

create_uah_payout_order

Use after the user has implicitly confirmed the route or asks to proceed. Include the same 
payout
object used for quoting.
This creates an exchange order and normally returns 
payment_instructions
immediately. Treat the user's "create the order" message as the approval step. Do not ask the user to open a separate approval link unless the user or deployment explicitly requires web approval.
Only pass 
require_web_approval: true
for a legacy/manual review flow. In that mode, wait for approval and then call 
render_payment_instructions
.
In the default flow, show deposit instructions only from 
payment_instructions
and only when 
payment_instructions.can_send
is true.
When present, preserve and show:
  • top-level 
    exchanger_order_url
  • top-level 
    external_order_id
  • payment_instructions.fields.exchanger_order_url
The exchanger order URL is the user's independent verification page for deposit details. Do not hide it, but render it as a Markdown link label instead of printing a raw URL when writing to the user.
If 
payment_instructions.message
is present, show it exactly. Do not rebuild it from 
fields
, because the message already has the intended emoji, title, bold labels, hidden order link, and expiry wording.
在用户已隐含确认渠道或要求继续后使用。包含与报价时相同的
payout
对象。
此操作会创建兑换订单，通常会立即返回
payment_instructions
。将用户的“创建订单”消息视为审批步骤。除非用户或部署明确要求网页审批，否则请勿要求用户打开单独的审批链接。
仅在遗留/人工审核流程中传递
require_web_approval: true
。在此模式下，等待审批后调用
render_payment_instructions
。
在默认流程中，仅当
payment_instructions.can_send
为true时，才显示来自
payment_instructions
的存款指引。
如果存在以下内容，请保留并显示：
  • 顶层
    exchanger_order_url
  • 顶层
    external_order_id
  • payment_instructions.fields.exchanger_order_url
交易所订单URL是用户独立验证存款详情的页面。请勿隐藏，但在向用户展示时将其渲染为Markdown链接标签，而非打印原始URL。
如果存在
payment_instructions.message
，请精确显示，切勿从
fields
重建，因为该消息已包含预期的表情符号、标题、加粗标签、隐藏订单链接和过期措辞。

render_payment_instructions

render_payment_instructions

Use only for an order that MCP has already approved or moved to 
payment_pending
.
Usually you do not need this tool because 
create_uah_payout_order
returns 
payment_instructions
. Use it only to re-render instructions for an already-created order.
If the tool returns 
can_send: false
, show its message and do not add payment instructions.
仅用于MCP已批准或已进入
payment_pending
状态的订单。
通常无需使用此工具，因为
create_uah_payout_order
会返回
payment_instructions
。仅在需要重新渲染已创建订单的指引时使用。
如果工具返回
can_send: false
，显示其消息且不添加支付指引。

get_order_status

get_order_status

Poll every 60 seconds after payment instructions are shown.
If 
provider_status
or 
provider_status_checked_at
is present, include it in status updates. Do not infer route-side progress from a balance probe.
If 
exchanger_order_url
is present, include it in status updates when the user is checking whether the order is still safe to fund.
Stop polling when the order is final.
显示支付指引后，每60秒轮询一次。
如果存在
provider_status
或
provider_status_checked_at
，请将其包含在状态更新中。切勿从余额探测推断渠道端进度。
如果存在
exchanger_order_url
，当用户询问订单是否仍可安全充值时，将其包含在状态更新中。
当订单进入最终状态时，停止轮询。

check_usdt_bep20_balance

check_usdt_bep20_balance

Use only as a diagnostic probe for a known deposit address. It does not replace order status and must not be used to infer approval.
仅作为已知存款地址的诊断探测工具使用。它不能替代订单状态，也不得用于推断审批状态。

User-Facing Messages

面向用户的消息

Reply in the user's conversation language. Keep messages compact and decision-oriented:
  1. Start with the outcome.
  2. Show the exact route as a bold line.
  3. Put amount, network, order ID, and verification link in scan-friendly lines.
  4. Before deposit, end with a short checklist.
  5. Never bury safety details in a long paragraph.
使用用户对话的语言回复。保持消息简洁且以决策为导向：
  1. 开头说明结果
  2. 将精确渠道显示为加粗行
  3. 将金额、网络、订单ID和验证链接放在易于扫描的行中
  4. 存款前以简短清单结尾
  5. 切勿将安全细节隐藏在长段落中

Route Found

找到渠道

text
Route found.

**119.84 USDT BEP20 -> Monobank UAH**

You receive: **5000 UAH**
You send: **119.84 USDT**
Network: **BEP20 / BNB Smart Chain**
Route: **route label returned by MCP**
Rate: **41.72 UAH**
Quote expires: **18:42 WITA**

AML: payment is subject to provider AML screening.

Say "create order" and I will create the exchange order and return exact deposit instructions.
text
已找到渠道。

**119.84 USDT BEP20 -> Monobank UAH**

您将收到：**5000 UAH**
您需发送：**119.84 USDT**
网络：**BEP20 / BNB Smart Chain**
渠道：**MCP返回的渠道标签**
汇率：**41.72 UAH**
报价过期时间：**18:42 WITA**

AML提示：支付需经过服务商AML筛查。

请回复“创建订单”，我将创建兑换订单并返回精确存款指引。

Payment Instructions

支付指引

text
✅ **Order ready**

**119.84 USDT BEP20 -> Monobank UAH**

🧾 **Order:** SL-483920
🔗 **Check order:** [open order page](https://exchanger.example/order/SL-483920/)
💵 **Amount:** **119.84 USDT**
⛓️ **Network:** **BEP20 / BNB Smart Chain**
🏦 **Address:** `0x...`
📝 **Comment/memo:** `SL-483920`
⏳ **Expires:** today at 18:42 WITA (10:42 UTC)

Check the order page once before sending.
Send the exact amount. Do not use another network. Do not reuse this order after expiry.
Payment is subject to provider AML screening.
If 
payment_instructions.fields.comment
is null or empty, omit the 
Comment/memo
line entirely. Do not write 
not required
.
If MCP does not return 
exchanger_order_url
, keep the same structure but replace the verification line with:
text
Verification link: MCP did not receive an exchanger order link for this order.
text
✅ **订单已就绪**

**119.84 USDT BEP20 -> Monobank UAH**

🧾 **订单号：** SL-483920
🔗 **查看订单：** [打开订单页面](https://exchanger.example/order/SL-483920/)
💵 **金额：** **119.84 USDT**
⛓️ **网络：** **BEP20 / BNB Smart Chain**
🏦 **地址：** `0x...`
📝 **备注/留言：** `SL-483920`
⏳ **过期时间：** 今日18:42 WITA（UTC时间10:42）

发送前请务必查看订单页面。
请发送精确金额，请勿使用其他网络，过期后请勿重复使用此订单。
支付需经过服务商AML筛查。
如果
payment_instructions.fields.comment
为null或空，完全省略
备注/留言
行，请勿写“无需备注”。
如果MCP未返回
exchanger_order_url
，保持相同结构，但将验证行替换为：
text
验证链接：MCP未返回此订单的交易所订单链接。

Under 60 Seconds

剩余时间不足60秒

text
Do not send.

This order expires in under 60 seconds. I will create a fresh one if you want to continue.
text
请勿发送资金。

此订单剩余过期时间不足60秒。如果您希望继续，我将创建新订单。

Completed

已完成

text
Payment received.

Order: SL-483920
Tx: 0x...
Status: completed
text
已收到支付。

订单号：SL-483920
交易哈希：0x...
状态：已完成

Support Needed

需要支持

text
Support needed.

Order: SL-483920
Route: route label returned by MCP
Reason: partial payment detected
Support: https://...
text
需要支持。

订单号：SL-483920
渠道：MCP返回的渠道标签
原因：检测到部分支付
支持链接：https://...

What Not To Do

禁止操作

Do not say:
text
Send any amount around 120 USDT.
Say:
text
Send exactly 119.84 USDT.
Do not say:
text
Send USDT.
Say:
text
Send USDT on BEP20 / BNB Smart Chain.
Do not say:
text
The order is probably still valid.
Say:
text
I need to check the order status before you send.
请勿说：
text
发送约120 USDT即可。
应说：
text
请发送精确的119.84 USDT。
请勿说：
text
发送USDT。
应说：
text
请在BEP20 / BNB Smart Chain网络发送USDT。
请勿说：
text
订单可能仍然有效。
应说：
text
在您发送前，我需要检查订单状态。

Fail-Closed Behavior

终止流程行为

If any required tool fails, stop the payment flow and explain the precise blocker:
  • contacts unavailable
  • contact details incomplete
  • quotes unavailable; if MCP returns supported ranges, show those ranges and ask whether the user wants to retry with a supported amount
  • order creation failed
  • approval expired
  • order expires in under 60 seconds
  • payment status unclear
  • provider status unclear
Never continue by guessing.
如果任何必需工具失败，停止支付流程并解释确切的阻塞原因：
  • 联系人不可用
  • 联系人详情不完整
  • 报价不可用；如果MCP返回支持范围，显示该范围并询问用户是否希望使用支持的金额重试
  • 订单创建失败
  • 审批已过期
  • 订单剩余过期时间不足60秒
  • 支付状态不明
  • 服务商状态不明
切勿通过猜测继续流程。