@itpay/cli 0.2.9 → 0.2.10

package/README.md

@@ -240,7 +240,7 @@ Payment QR rules:
 - Use `mobile_wallet_url` only as a human mobile fallback.
 - Do not generate your own QR from payment URLs.
 - If you know the current chat channel and `render_plan.platforms.<channel>` exists, use that branch before `render_plan.selected`.
-- In OpenClaw Telegram, send `render_plan.platforms.telegram.openclaw_message` with OpenClaw `message send --media ... --presentation ...`; do not put legacy inline media directives inside human prose.
+- In OpenClaw Telegram, send `render_plan.platforms.telegram.openclaw_message.command_args` with `openclaw message send`; its `presentation.blocks[].buttons[]` uses native `text/url/callback_data`.
 - If the channel is unsupported, use `render_plan.selected.fallback` / plain chat. Do not rewrite the chosen plan into a custom table or omit the real URL.
 - If status is `payment_handoff_required`, `next` is the human reply step, not payment wait.
 - Treat only `payment_intent.verified` as payment success.

package/docs/agent/buyer/payment-qr.json

@@ -46,7 +46,7 @@
     "Do not rewrite the chosen render plan into a custom table. Use its text/markdown, media, links, and buttons as provided.",
     "If selected.links exists, include the real URL. Do not only show the link label.",
     "If selected.buttons exists but the current adapter cannot render native buttons, degrade to selected.links plus short text; do not fake payment success or skip the status check.",
-    "In OpenClaw Telegram, prefer response.render_plan.platforms.telegram.openclaw_message: send its message/media/presentation through OpenClaw message send. Do not place legacy inline media directives inside prose; that fallback cannot render inline buttons.",
+    "In OpenClaw Telegram, prefer response.render_plan.platforms.telegram.openclaw_message.command_args with openclaw message send. Its presentation.blocks[].buttons[] uses native text/url/callback_data; do not simulate buttons in normal prose.",
     "In Codex or Claude Code app clients, send response.human_visible_markdown or response.render_plan.platforms.codex_app.markdown to the human first. Do not start a hidden long wait before the human-visible message is sent.",
     "For Telegram-style message clients, use response.render_plan.platforms.telegram: send photo media first, include links, and expose native buttons for refresh/status when the adapter supports them.",
     "For plain chat clients, show response.human_visible_markdown and stop unless the human asks you to check status or returns with a payment question.",

package/docs/agent/buyer/quickstart.json

@@ -68,7 +68,7 @@
     "Show the returned payment QR exactly as provided before starting payment wait.",
     "Payment truth comes only from payment_intent.verified.",
     "Secure delivery goes to the human first; report redacted delivery status only.",
-    "When a response includes render_plan, first use render_plan.platforms.<current channel> if it exists. If selected.platform is current_channel_required, selected.fallback is only for unsupported plain chat. In OpenClaw Telegram, use render_plan.platforms.telegram.openclaw_message instead of handwritten legacy media directive prose."
+    "When a response includes render_plan, first use render_plan.platforms.<current channel> if it exists. If selected.platform is current_channel_required, selected.fallback is only for unsupported plain chat. In OpenClaw Telegram, pass render_plan.platforms.telegram.openclaw_message.command_args to openclaw message send instead of handwritten prose."
   ],
   "forbidden": [
     "Do not call ops commands from the buyer path.",

package/lib/render-human.js

@@ -389,16 +389,16 @@ function openclawTelegramMessage({ action = {}, media = [], links = [], buttons
   const text = action.kind === "payment_qr"
     ? "请扫码或点击链接完成支付。付款完成后点“我已付款，查询状态”，或直接回复“我已付款”。"
     : "请打开 ItPay 授权入口，完成后回到当前对话。";
-  const presentationButtons = links.map((link) => ({ label: link.label, url: link.url }));
+  const presentationButtons = links.map((link) => openclawURLButton(link.label, link.url));
   if (action.kind === "payment_qr") {
     presentationButtons.push(
-      { label: "支付遇到问题 / 刷新", action: { type: "command", command: "刷新付款二维码" } },
-      { label: "我已付款，查询状态", action: { type: "command", command: "我已付款，查询状态" } }
+      openclawCallbackButton("支付遇到问题 / 刷新", "refresh_payment_qr", action),
+      openclawCallbackButton("我已付款，查询状态", "check_payment_status", action)
     );
   } else {
     for (const button of buttons) {
       if (button.url && !presentationButtons.some((item) => item.url === button.url)) {
-        presentationButtons.push({ label: button.text || "打开链接", url: button.url });
+        presentationButtons.push(openclawURLButton(button.text || "打开链接", button.url));
       }
     }
   }
@@ -419,10 +419,23 @@ function openclawTelegramMessage({ action = {}, media = [], links = [], buttons
       message: text,
       media: mediaURL || undefined,
       presentation
-    })
+    }),
+    callbacks: action.kind === "payment_qr" ? {
+      refresh_payment_qr: "收到 callback_data 后刷新或重新发送同一个 payment_intent 的付款入口。",
+      check_payment_status: "收到 callback_data 后运行 buyer payment wait/status，只信 payment_intent.verified。"
+    } : undefined
   });
 }
 
+function openclawURLButton(text, url) {
+  return compactObject({ text, url });
+}
+
+function openclawCallbackButton(text, intent, action = {}) {
+  const id = action.payment_intent_id || action.id || "current";
+  return { text, callback_data: `itp:${intent}:${id}` };
+}
+
 function selectedRenderPlatform(host = "") {
   const normalized = String(host || "").toLowerCase().replaceAll("-", "_");
   if (["codex", "codex_app", "codex_cli"].includes(normalized)) return "codex_app";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@itpay/cli",
-  "version": "0.2.9",
+  "version": "0.2.10",
   "description": "ItPay CLI, buyer skill, and agent-readable docs for agent-native commerce.",
   "type": "module",
   "bin": {

package/skills/itpay-buyer/SKILL.md

@@ -214,8 +214,9 @@ local QR image path for clients that cannot render remote SVG reliably. In
 agent/chat clients, prefer `--no-wait-payment`: if you know the current channel
 and `render_plan.platforms.<channel>` exists, use that branch first. In Codex
 or Claude Code app clients, send the platform markdown exactly. In OpenClaw
-Telegram, use `render_plan.platforms.telegram.openclaw_message` so media and
-native buttons are sent through the adapter. If `selected.platform` is
+Telegram, pass `render_plan.platforms.telegram.openclaw_message.command_args`
+to `openclaw message send` so media and native `text/url/callback_data` buttons
+are sent through the adapter. If `selected.platform` is
 `current_channel_required`, `selected.fallback` is only for unsupported plain
 chat clients. Do not invent a table or rewrite the UI plan.