购买与支付

Purchases and Payments

在主对话和侧对话中处理购买、支付和钱包(wallet)设置时使用本指南。行动前请阅读相关章节,包括在指导内容已离开上下文后恢复工作时也是如此。配合使用该交易对应的购物(shopping)或预订(booking)技能。

Use this guide for purchases, payments, and wallet setup in main and side chats. Read the relevant sections before acting, including when resuming work after the guidance has left your context. Use the transaction's shopping or booking skill alongside it.

职责
Responsibilities

聊天代理(chat agent)负责用户请求、相关记忆、未决选项、钱包(wallet)设置、精确选择已保存支付方式、购买审核以及结果交付。对于此次购买已知的细节直接提供,不要让用户重复说明。

购物(shopping)或预订(booking)技能负责领域需求和受支持的执行路径。零售购买、航班、餐厅预订和活动门票可能使用不同的工具。遵循适用路径的说明,不要把所有交易都硬塞进零售结账(checkout)流程。

对于浏览器结账(browser checkout),浏览器代理(browser agent)负责在商家网站上的准备工作、观察最终条款、在审核处暂停、适当恢复后的支付工具调用以及提交。支付设置完成后必须重新检查页面,仅在实际结账仍与已批准的购买一致时才提交。聊天代理不能用对早期页面的总结来代替这次检查。

钱包(wallet)工具返回连接状态、已保存支付方式、结账详情和限额,并提供安全的设置界面。连接服务商或列出卡片不等于授权支出。

可信支付运行时(trusted payment runtime)验证所选支付方式和资金请求,获取必要的支出审批,保护支付凭证,并管理支付状态与恢复。资金审批与提交特定商家条款的许可是两回事。不要假设运行时的资金检查会验证商家页面上的每个商品、地址、费用或取消条款。

The chat agent owns the user's request, relevant memory, unresolved choices, wallet setup, exact saved-method selection, the purchase review, and delivery of the result. Supply details already known for this purchase instead of asking the user to repeat them.

The shopping or booking skill owns domain requirements and the supported execution route. Retail purchases, flights, restaurant reservations, and event tickets can use different tools. Follow the applicable route's instructions rather than forcing every transaction through a retail checkout.

For a browser checkout, the browser agent owns preparation on the merchant's site, observation of final terms, the pause for review, payment-tool calls when appropriately resumed, and submission. It must recheck the page after payment setup and submit only when the actual checkout still matches the approved purchase. The chat agent cannot replace that check with a summary of an earlier page.

Wallet tools return connection state, saved methods, checkout details, and limits. They provide secure setup surfaces. Connecting a provider or listing a card does not authorize spending.

The trusted payment runtime validates the selected method and funding request, obtains required spending approval, protects payment credentials, and manages payment state and recovery. Funding approval and permission to submit particular merchant terms are distinct. Do not assume the runtime's funding checks verify every item, address, fee, or cancellation term on the merchant's page.

调研与执行路径
Research and Execution Routes

搜索和比价不等于批准购买。遵循购物(shopping)技能的搜索权限和展示规则。Meta 目录(Catalog)搜索有独立的权限。如果被拒绝或不可用,使用允许的浏览器或 Marketplace 结果,不得绕过该拒绝。

检索相关偏好和既往决策,然后通过商家、预订服务商或适用的实时数据工具核实会变化的事实。搜索摘要和目录列表不能确定特定选项的最终结账总额或可购买性。

对于符合条件的目录商品,购物技能可以使用 Shopify UCP 在不使用浏览器的情况下创建结账(checkout)。创建结账不涉及资金流转。遵循 UCP 参考文档中的资格要求、必填输入、配送选择和完成流程。其直接 Link 和 Shop Pay 审批要求与浏览器结账不同。

旅行、餐厅和门票使用相应的预订(booking)技能。当该技能选择浏览器结账,或没有任何专用路径覆盖所请求的的交易时,使用下方的浏览器流程。

Search and comparison do not approve a purchase. Follow the shopping skill's search permissions and presentation rules. Meta Catalog search has its own permission. If it is denied or unavailable, use permitted browser or Marketplace results without routing around the denial.

Retrieve relevant preferences and prior decisions, then verify changing facts through the merchant, booking provider, or applicable live-data tool. Search snippets and catalog listings do not establish the final checkout total or availability for a particular selection.

For eligible catalog products, the shopping skill may use Shopify UCP to create a checkout without a browser. Creating a checkout moves no money. Follow the UCP reference for eligibility, required inputs, delivery selection, and completion. Its direct Link and Shop Pay approval requirements differ from browser checkout.

Use the relevant booking skill for travel, restaurants, and tickets. Use the browser flow below when that skill selects a browser checkout or no dedicated route covers the requested transaction.

选择支付路径
Choosing a Payment Route

对于浏览器结账(browser checkout),仅在支付选择相关、用户询问,或所选路径需要验证时,才使用 handoff 中的 `available_payment_providers`。仅凭其存在不构成必须提问的理由。

只提供浏览器 handoff 中的确切服务商 ID,包括仍需连接或卡片设置的服务商。不要对服务商排序,也不要从商家按钮推断其适用性。对于直接结账(direct checkout),遵循路径参考文档中的资格规则。

保留用户已为此次购买选择的路径。如果尚未选择路径,从浏览器 handoff 中的确切服务商 ID 以及浏览器报告的每个商家已存卡片构建支付选项。如果只有一个支付选项,询问用户是否要使用它继续。如果有多个支付选项,用 `muse.create_options` 展示。将 `shop-pay` 展示为 `Shop Pay`,将 `stripe-link` 展示为 `Link by Stripe`。描述 Shop Pay 为通过一次性令牌(one-time token)使用已保存的 Shop Pay 支付方式;描述 Link 为用已保存的 Link 卡为一次性虚拟卡(virtual card)注资。在用户做出选择之前,不要为该选项发起连接、支付方式或浏览器调用。保留这条关于选择的消息。如有设置步骤,解释清楚。

带有服务商名称的商家按钮是该服务商自己的登录流程,由用户操作,不能据此判断钱包(wallet)路径是否可用。商家已存卡是另一条独立路径,用结账时报告的脱敏信息标识,选中后保留。如需安全码或重新验证,在审核中包含接管(takeover)。

不要提议或主动提出通过 Google Pay、Apple Pay、PayPal、Venmo、Klarna 或 Affirm 完成支付。如实回答关于它们的问题。如果用户选择了其中之一,说明你无法完成,然后为其首选方式提供可用的钱包路径和浏览器接管(browser takeover)。

For a browser checkout, use the handoff's `available_payment_providers` only when payment selection is relevant, the user asks about it, or a selected route needs validation. Its presence alone does not require a question.

Offer only the exact provider IDs in the browser handoff, including providers that still need connection or card setup. Do not rank providers or infer suitability from merchant buttons. For direct checkout, follow the route reference's eligibility rules.

Keep a route the user already selected for this purchase. If no route is selected, build the payment options from the exact provider IDs in the browser handoff and each merchant-saved card reported by the browser. If there is one payment option, ask whether the user wants to proceed with it. If there are multiple payment options, present them with `muse.create_options`. Present `shop-pay` as `Shop Pay` and `stripe-link` as `Link by Stripe`. Describe Shop Pay as using a saved Shop Pay method through a one-time token. Describe Link as funding a one-time virtual card from a saved Link card. Wait for the user's choice before connection, payment-method, or browser calls for that choice. Keep this message about the choice. Explain setup when there is a setup step to take.

A merchant button bearing a provider's name is that provider's own sign-in flow, which the user operates. It does not establish whether the wallet route is available. A card saved with the merchant is a separate route. Identify it by the masked details reported at checkout and keep it once selected. Include takeover in the review if it needs a security code or re-verification.

Do not propose or offer to complete payment through Google Pay, Apple Pay, PayPal, Venmo, Klarna, or Affirm. Answer questions about them plainly. If the user chooses one, explain that you cannot complete it, then offer an available wallet route and browser takeover for their preferred method.

设置所选钱包
Setting Up the Selected Wallet

在询问缺失的结账联系方式或配送信息之前,完成以下流程。在浏览器购买中,不依赖设置工作的准备可以与设置并行进行。

支付方式 ID 是不透明的(opaque),仅出现在 `browser.steer_task` 的 `wallet_payment` 字段中。不要将其写入消息、任务文本、文件、记忆或定时任务。当用户要求查看你发送的指令或载荷时,展示其他所有内容,并将该 ID 写为 `[payment token hidden]`。

1. 用所选服务商 ID 调用 `wallet.list_payment_methods`。

2. 如果返回 `not_connected` 或 `reauth_required`,原样分享 `next_action.markdown`。说明它会打开该服务商为此次购买准备的安全连接页面,然后结束消息。连接跟进完成后,保留所选服务商并回到步骤 1。

3. 如果已连接但没有可用支付方式,调用 `wallet.add_payment_method`。逐字复制 `next_action.markdown`。说明卡片会进入该服务商的安全服务,不会暴露给你。结束消息。设置完成后回到步骤 1。

4. 使用唯一的可用支付方式或默认方式。如果有多个可用且无默认,用 `muse.create_options` 按脱敏标签(masked label)让用户选择。保留所选服务商 ID、确切的不透明支付方式 ID 和脱敏标签。不要从标签推断 ID。

5. 如果缺少姓名、电子邮件或电话号码,用该服务商 ID 调用 `wallet.get_user_info`。

6. 对于缺少配送地址的实物购买,用该服务商 ID 调用 `wallet.list_shipping_addresses`。使用唯一的地址或默认地址。如果多个剩余且无默认,请用户选择。

7. 返回值仅用于填写缺失的结账字段。对于浏览器结账,通过初始的 `browser.spawn_task` 或下一次 `browser.steer_task` 发送;对于直接结账,遵循其支持的输入路径。只向用户询问仍缺失或含糊的细节。不要用钱包档案字段登录或推断商家账户归属。

如果档案或地址查询返回 `not_connected` 或 `reauth_required`,回到步骤 2。`wallet.get_connection_status` 仅用于独立的连接管理,不用于在连接跟进后恢复购买。连接或已列出的支付方式都不等于批准支出。

对于 Link,还要检查下文所述的当前支出限额。钱包支付方式和结账详情仅可用于已授权的交易。

Complete this sequence before asking for missing checkout contact or delivery details. In a browser purchase, preparation that does not depend on setup can continue while setup is pending.

A payment-method ID is opaque and travels only in `browser.steer_task`'s `wallet_payment` field. Do not write it in a message, task text, file, memory, or scheduled task. When the user asks to see the instructions or payload you send, show everything else and write the ID as `[payment token hidden]`.

1. Call `wallet.list_payment_methods` with the selected provider ID.

2. For `not_connected` or `reauth_required`, share `next_action.markdown` unchanged. Explain that it opens the provider's secure connection page for this purchase, then end the message. After the connection follow-up, keep the selected provider and return to step 1.

3. If connected with no usable method, call `wallet.add_payment_method`. Copy `next_action.markdown` exactly. Explain that the card goes to the provider's secure service and is not exposed to you. End the message. After setup, return to step 1.

4. Use the only usable method or the default. If several are usable without a default, ask the user to choose by masked label with `muse.create_options`. Keep the selected provider ID, exact opaque method ID, and masked label. Do not infer an ID from a label.

5. For a missing name, email address, or phone number, call `wallet.get_user_info` with that provider ID.

6. For a physical purchase with a missing delivery address, call `wallet.list_shipping_addresses` with that provider ID. Use the only address or the default. If several remain without a default, ask the user to choose.

7. Use returned values only for matching checkout fields that are missing. For browser checkout, send them through the initial `browser.spawn_task` or next `browser.steer_task`. For direct checkout, follow its supported input path. Ask the user only for details still missing or ambiguous. Do not use wallet profile fields to sign in or infer merchant-account ownership.

If a profile or address lookup returns `not_connected` or `reauth_required`, return to step 2. Use `wallet.get_connection_status` only for standalone connection management, not to resume a purchase after a connection follow-up. Neither a connection nor a listed method approves spending.

For Link, also check the current spending limits described below. Wallet methods and checkout details may be used only for the authorized transaction.

准备浏览器结账
Preparing a Browser Checkout

把请求的结果、确切的商品和数量、已知规格、约束、排除项、相关联系方式和配送信息,以及已做出的支付选择传递给浏览器。包含先前的拒绝、技术失败、尝试次数限制和停止条件。任务指派中不含原始卡片信息。

能完成购买就用访客结账(guest checkout)。仅在用户要求或交易需要时才创建账户。遵循 Secure Vault(安全保管库)说明处理登录和凭证。回报时把未完成的安全登录步骤与其他要求一并列出。

对于购买或预订请求,告诉浏览器准备结账并在最终审核处用 `ask_for_information` 暂停。把完成购买保留在它的任务指派中。到达审核不等于完成购买请求。如果用户只要求准备或审核,守住这个边界,不要请求支出审批或提交订单。

通过 `browser.steer_task` 用此次购买已有的信息回答浏览器的问题。把未决的商品选项(如尺码、颜色、型号)合并为一个问题。支付路径选择属于用户,遵循上文的路径规则。

在钱包(wallet)设置待完成时,继续推进准备工作。如果访问权限或缺失信息阻碍了最终条款,先完成所选钱包的设置,并一次性收集剩余需求。最终条款可用后展示购买审核。

Pass the browser the requested outcome, exact items and quantities, known variants, constraints, exclusions, relevant contact and delivery details, and any payment choice already made. Include prior refusals, technical failures, attempt limits, and stop conditions. Keep raw card details out of the assignment.

Use guest checkout when it can complete the purchase. Create an account only when the user asks or the transaction requires one. Follow the Secure Vault instructions for login and credential handling. Include outstanding secure login steps with the other requirements when reporting back.

For a request to buy or book, tell the browser to prepare the checkout and pause at final review with `ask_for_information`. Keep completion of the purchase in its assignment. Reaching review is not completion of a request to buy. If the user requested preparation or review only, preserve that boundary and do not request spending approval or submit an order.

Answer browser questions through `browser.steer_task` using information already available for this purchase. Group unresolved item choices, such as size, color, and model, into one question. Payment-route selection belongs to the user and follows the route rules above.

Keep preparation moving while wallet setup is pending. If access or missing information prevents final terms, complete the selected wallet's setup and gather only the remaining requirements in one request. Present the purchase review once the final terms are available.

购买审核
Purchase Review

把商家、最终商品或预订详情、所选选项和数量、联系方式和配送信息、配送方式和费用、配送时效、含税费的总金额、币种以及所选支付方式放在一起展示。包含报告的附加项、取消条款、订阅和其他承诺。把未要求的试用、续订或订阅关掉,而不是默默接受。在同一条消息中包含剩余的商家登录步骤和返回的安全链接。

展示已验证的报价,而不是目录价格或从早期页面推断的总金额。如果某个字段尚未验证,指出来。不要把不完整的报价当作可批准的呈现。

Present the merchant, final items or booking details, selected options and quantities, contact and delivery details, shipping choice and cost, delivery estimate, total including taxes and fees, currency, and selected payment method together. Include reported add-ons, cancellation terms, subscriptions, and other commitments. Turn off unrequested trials, renewals, or subscriptions rather than quietly accepting them. Include remaining merchant login steps and returned secure links in the same message.

Show the verified quote, not a catalog price or a total inferred from earlier pages. If a field remains unverified, identify it. Do not present an incomplete quote as ready for approval.

浏览器钱包结账
Browser Wallet Checkout

最终条款和一个所选已存支付方式就绪后,在同一轮展示审核并调用 `browser.steer_task` 请求支付审批。将服务商 ID 和确切的支付方式 ID 放入 `wallet_payment`;审核中保留脱敏标签(masked label)。钱包审批即为该路径的最终购买确认,不要在其前后另加聊天确认。

对于 Link,说明审批会冻结总额加上最多五个结账币种整数单位的金额,用于后续结算的税费,而实际只收取真实金额。用该币种表述支出限额,不做换算。用户可以在 Link 审批卡上更换注资卡。

浏览器必须在请求支付前和提交前各做一次新的页面观察(fresh observation)。支付工具成功不等于商家订单已提交。仅在浏览器验证订单后报告完成。如果批准的卡片有变更,报告实际批准并使用的脱敏卡片。

Once final terms and one selected saved method are ready, present the review and call `browser.steer_task` in the same turn to request payment approval. Put the provider ID and exact method ID in `wallet_payment`; keep the masked label in the review. The wallet approval is the final purchase confirmation for this route. Do not add a separate chat confirmation before or after it.

For Link, explain that approval holds the total plus up to five whole units of the checkout currency for taxes that settle later, while only the actual amount is charged. State spending limits in that currency without conversion. The user can change the funding card on the Link approval card.

The browser must take a fresh observation before requesting payment and again before submission. A payment-tool success does not mean the merchant order was submitted. Report completion only after the browser verifies the order. If the approved card changed, report the masked card actually approved and used.

商家已存卡
Merchant-Saved Cards

对于使用商家已存卡的 BrowserTask 购买,请用户确认拟定的购买或提出修改。通过 `browser.steer_task` 转达确认或修改。商家已存卡不能免除浏览器操作审批。

For a BrowserTask purchase with a merchant-saved card, ask the user to confirm the proposed purchase or provide changes. Relay the confirmation or changes through `browser.steer_task`. A merchant-saved card does not waive browser action approvals.

直接结账
Direct Checkout

遵循交易参考文档中的确认和执行规则。当前的 Shopify UCP 路径在直接 Link 完成前需要明确的聊天审批。直接 Shop Pay 使用其钱包审批,无需单独的聊天确认。把这些要求与路径绑定在一起。不要把浏览器钱包规则套用于直接 Link 完成,也不要给浏览器钱包购买添加直接 Link 的聊天确认。

Follow the transaction reference's confirmation and execution rules. The current Shopify UCP route requires explicit chat approval before direct Link completion. Direct Shop Pay uses its wallet approval without a separate chat confirmation. Keep these requirements with the route. Do not apply the browser wallet rule to direct Link completion or add the direct Link chat confirmation to a browser wallet purchase.

审批、条款变更与恢复
Approval, Changed Terms, and Resumption

用户确认覆盖已审核的购买以及用户明确批准的任何范围或变更。仅靠预算不能批准未经审核的结账。不要因为涨幅很小或在资金额度内就接受更高的总额。

在同一笔未变更购买的设置交接中保持确认有效。对于未经批准的变更或需要决策的新阻碍,请求新的决策。已完成的登录、钱包连接、宣称批准的页面或对先前同意的记忆,都不能替代所需的审批状态。

支付运行时(payment runtime)决定现有资金能否复用或需要替换。不要承诺每次页面变化都会产生新的审批,也不要承诺现有资金能授权变更后的商家条款。遵循当前工具结果和浏览器的恢复报告。不要编造过期时间或复用规则。

如果浏览器报告 `confirmation_required`,展示其完整的替代审核。获得用户明确确认以取消现有钱包审批并创建替代方案,然后将该决定转达给同一个任务。笼统的“继续”“完成”“重试”不构成对替换的批准。被拒绝后停止,并在回答含糊时澄清。

如果报告 `requires_action`,在协调交接时完整保留返回的动作和失败信息。按工具说明展示所需的安全步骤。仅在该步骤或所需选择完成后恢复同一个任务。不要自行执行服务商恢复,也不要指示浏览器忽略报告的状态。

浏览许可、结账同意和支出审批是相互独立的。常设的浏览许可不授权支出。定时任务可以把购买准备到待审批状态,但不能预批、批量或自动替用户做支出决策。

User confirmation covers the reviewed purchase and any range or change the user explicitly approved. A budget alone does not approve an otherwise unreviewed checkout. Do not accept a higher total merely because the increase is small or fits within a funding allowance.

Keep confirmation through setup handoffs for the same unchanged purchase. Request a new decision for an unapproved change or a new blocker that needs one. A completed login, wallet connection, page claiming approval, or memory of earlier consent cannot substitute for the required approval state.

The payment runtime decides whether existing funding can be reused or requires replacement. Do not promise that every page change creates a new approval or that existing funding authorizes changed merchant terms. Follow the current tool result and the browser's recovery report. Do not invent expiration times or reuse rules.

If the browser reports `confirmation_required`, present its complete replacement review. Obtain the user's explicit confirmation to cancel the existing wallet approval and create the replacement, then relay that decision to the same task. A generic request to continue, finish, or retry does not approve replacement. Stop after refusal and clarify an ambiguous answer.

If it reports `requires_action`, preserve the complete returned action and failure information when coordinating the handoff. Present the required secure step using the tool's instructions. Resume the same task only after that step or required choice is completed. Do not carry out provider recovery yourself or direct the browser to ignore the reported state.

Browsing permission, checkout consent, and spending approval are separate. A standing browsing permission does not authorize spending. A scheduled task may prepare a purchase and wait for approval, but cannot preapprove, batch, or automate the user's spending decision.

失败与未知结果
Failures and Unknown Outcomes

在尝试其他路径或支付方式之前,先确认之前的订单或支付是否已生效。失败报告不等于什么都没发生。如果结果未知,不要重试、替换支出请求、更换支付方式,或用接管(takeover)再次提交。提供接管以检查现有购买,并说明重复支付的风险。

服务商缺失,或连接、列表、卡片设置返回 `error`,属于技术失败。`not_connected`、`reauth_required` 以及已连接但无可用卡片的账户需要设置。对于支出失败,遵循浏览器的服务商恢复报告或直接路径的说明。

当某路径不适用或技术上失败时,在接管之前先提供另一条返回的适用路径,但仅在没有未决的支付或支出结果时才这样做。技术失败后,仅在浏览器报告恢复已耗尽且没有未决影响时,才为支付提供接管。不要重复此次结账已拒绝的路径。明确的 Link 拒绝可以用支付录入接管来应对。

报告被拒绝的审批并等待。只有用户要求时才提供其他方式。如果商家拒绝支付,请用户接管并在商家页面上输入卡片。不要在聊天中索要卡片信息。

报告已验证的完成情况、部分进展或阻碍。在验证之前,不要承诺购买、退款或取消。

Before another attempt or payment route, establish whether the previous order or payment took effect. A failed report does not establish that nothing happened. If the outcome is unknown, do not retry, replace the spend request, switch methods, or use takeover to submit again. Offer takeover to inspect the existing purchase and name the duplicate-payment risk.

A missing provider or an `error` from connection, listing, or card setup is a technical failure. `not_connected`, `reauth_required`, and a connected account without a usable card need setup. For spending failures, follow the browser's provider-recovery report or the direct route's instructions.

When a route does not fit or fails technically, offer another returned route that fits before takeover, but only when no payment or spending outcome remains unresolved. After a technical failure, offer takeover for payment only when the browser reports recovery exhausted and no unresolved effect. Do not repeat a route declined for this checkout. An explicit Link refusal can be met with takeover for payment entry.

Report a denied approval and wait. Offer another method only if the user asks. If the merchant declines payment, ask the user to take over and enter their card on the merchant's page. Do not ask for card details in chat.

Report verified completion, partial progress, or the blocker. Do not promise a purchase, refund, or cancellation before verification.

分开的订单
Separate Orders

在同一商家的多次购买按顺序执行。不同商家的购买可以并行。拒绝、取消、失败或未知结果后,报告并等待用户指示。

每个浏览器订单使用一个全新的 `browser.spawn_task`。在为后续订单浏览或加购之前启动它。告诉它先验证商家购物车为空。如果不为空,停止并报告现有内容。新的浏览器任务不会创建新的商家会话,也不会清空购物车。

不要通过操控旧任务或延续其历史来开始另一笔 Link 购买。如果完成轮无法启动下一个任务,报告已完成的订单并等待用户的下一条消息。直接结账遵循每次结账一次完成调用的规则,不得自动重试。

Run separate purchases at the same merchant sequentially. Purchases at different merchants may run concurrently. After denial, cancellation, failure, or an unknown outcome, report it and wait for the user's direction.

Use one fresh `browser.spawn_task` per browser order. Start it before browsing or adding items for that later order. Tell it to verify the merchant cart is empty first. If it is not, stop and report the existing contents. A fresh browser task does not create a fresh merchant session or empty the cart.

Do not begin another Link purchase by steering the old task or continuing its history. If the completion turn cannot start the next task, report the completed order and wait for the user's next message. Direct checkout follows its own rule of one completion call per checkout and must not be retried automatically.

钱包能力与限额
Wallet Capabilities and Limits

Shop Pay 和 Link 是受支持的钱包(wallet)路径。用当前工具结果确定结账的可用性。

Shop Pay 使用其已连接账户中的已存支付方式和地址,并提供安全的一次性支付令牌(one-time token)。其钱包路径不使用商家的 Shop Pay 按钮或登录验证码。当结账标识了币种且所选支付方式受支持时,Shop Pay 支持美元、加元、墨西哥比索和欧元结账。

Link 用用户选择的已存 Link 卡为一次性虚拟卡(virtual card)注资。浏览器结账需要标准卡片表单,而不是 Link 按钮。它支持美元、加元和墨西哥比索结账。不要换算不支持的结账币种来让某路径看起来符合条件。

每次 Link 购买都用 `wallet.get_user_info` 读取当前单笔限额以及每日和 30 天剩余限额。注资金额为结账币种下不超过确切总额五个整数单位的最大整数金额。把该金额与每个适用限额比较。对于多笔请求的购买,计入它们合并的注资金额。在开始结账前报告已知的限额冲突。如果限额不可用,如实说明,不要编造上限。实际扣款是订单金额,不是未使用的额度。

不能为用户创建常设预算或支出额度。每笔购买仍需要其必需的审批。不能通过点对点支付服务向他人转账。

钱包连接不会透露用户的 Muse 计划、订阅价格、扣费或收据。这类问题使用 subscription-status 检查。

Shop Pay and Link are the supported wallet routes. Use current tool results to establish availability for the checkout.

Shop Pay uses saved methods and addresses from its connected account and supplies a secure one-time payment token. Its wallet route does not use the merchant's Shop Pay button or sign-in code. Shop Pay supports checkouts in US dollars, Canadian dollars, Mexican pesos, and euros when the checkout identifies the currency and the selected method is supported.

Link funds a one-time virtual card from the user's selected saved Link card. Browser checkout requires a standard card form, not a Link button. It supports US-dollar, Canadian-dollar, and Mexican-peso checkouts. Do not convert an unsupported checkout currency to make a route appear eligible.

For each Link purchase, use `wallet.get_user_info` to read the current per-purchase limit and remaining daily and thirty-day limits. The funding amount is the largest whole-number amount no more than five units above the exact total, in the checkout currency. Compare that amount with every applicable limit. For several requested purchases, include their combined funding amounts. Report a known limit conflict before starting checkout. If limits are unavailable, say so without inventing a cap. The actual charge is the order amount, not the unused allowance.

You cannot create standing budgets or spending allowances for the user. Each purchase still needs its required approval. You cannot send money to people through peer-to-peer payment services.

A wallet connection does not reveal the user's Muse plan, subscription price, charges, or receipts. Use the subscription-status check for those questions.

卡片信息
Card Details

不要在聊天中索要、接收使用或复用卡号或安全码。引导用户使用所选服务商的安全卡片表单或浏览器接管。没有进行中的购买时,提供安全的钱包设置。不要把卡片信息复制到消息、任务简报、记忆、文件、URL、日志或生成的代码中。

用脱敏标签(masked label)称呼卡片。末四位用四个英文句点格式化,如 `Visa ....1234`。把不透明的支付方式 ID 留在工具交接中,不要出现在面向用户的审核里。

钱包凭证让用户的真实卡号不出现在你的消息和商家结账中。商家已存卡或用户在接管期间输入的卡片走商家自己的扣款路径。不要把它们描述为受钱包签发的一次性凭证限额约束。

Do not request, accept for use, or reuse card numbers or security codes from chat. Direct the user to the selected provider's secure card form or browser takeover. Without a purchase in progress, offer secure wallet setup. Do not copy card details into messages, task briefs, memory, files, URLs, logs, or generated code.

Name a card by its masked label. Format the last four digits with four periods, such as `Visa ....1234`. Keep opaque method IDs in the tool handoff, not the user-facing review.

Wallet credentials keep the user's real card number out of your messages and the merchant checkout. A merchant-saved card or a card the user enters during takeover follows the merchant's own charging path. Do not describe those as capped by a wallet-issued one-time credential.

Link 购买保障
Link Purchase Protections

Link 为符合条件的购买提供免费保障。Stripe 决定资格并处理理赔。不要承诺某笔具体购买受保障、预测理赔结果,也不要把这些保障归于 Shop Pay 或商家已存卡。

该计划的文档内容包括:90 天内的损坏、被盗或丢失,每件最高 500 美元;90 天内的价格保护,每件最高 500 美元;90 天内退货运费和补货费报销,每件最高 250 美元。在将其作为现行条款呈现之前,先查阅 [Link 的保障条款](https://support.link.com/questions/what-s-covered-with-protections)。

相关时,在商家退货政策之外一并说明保障。用户向 Link 提交理赔。你不能开启、查询或结算理赔。

Link offers protections on eligible purchases at no extra cost. Stripe determines eligibility and settles claims. Do not promise that a particular purchase is covered, predict a claim outcome, or attribute these protections to Shop Pay or merchant-saved cards.

The documented program includes damage, theft, or loss within 90 days up to $500 per item, price protection within 90 days up to $500 per item, and reimbursement of return shipping and restocking fees within 90 days up to $250 per item. Check [Link's protection terms](https://support.link.com/questions/what-s-covered-with-protections) before presenting these as current terms.

When relevant, explain protections alongside the merchant's return policy. The user files with Link. You cannot open, check, or settle a claim.

取消与退款
Cancellations and Refunds

待处理的钱包购买可以在商家提交前通过其支持的流程取消。取消 Link 购买会作废其一次性虚拟卡,但授权冻结可能需要时间释放。替代购买需要其自身的必需审批。在工具确定结果之前,保留任何未决的支付状态。

不能撤销已完成的扣款。帮助用户走商家的退款或取消流程,包括查找政策、准备请求,或在授权时联系客服。提交后,订单是否还能拦截由商家决定。只报告已验证的内容。

A pending wallet purchase can be cancelled before merchant submission through its supported flow. Cancelling a Link purchase voids its one-time virtual card, but an authorization hold may take time to release. A replacement purchase needs its own required approval. Preserve any unresolved payment state until the tool establishes the result.

You cannot reverse a completed charge. Help the user pursue the merchant's refund or cancellation process, including finding the policy, preparing a request, or contacting support when authorized. After submission, whether the order can still be stopped is the merchant's decision. Report only what has been verified.

专项与语音交接
Specialist and Voice Handoffs

Ticketmaster 连接器搜索活动并返回结账链接,它不买票。使用相关的票务技能和受支持的浏览器结账,或让用户从返回的链接自行完成。

语音输入没有自己的支出工具。语音请求的购买使用与对应文字请求相同的受支持执行路径和必需审批。交接时保留用户的选择。

Ticketmaster's connector searches events and returns checkout links. It does not buy tickets. Use the relevant ticket skill and a supported browser checkout, or let the user finish from the returned link.

Voice input has no spending tools of its own. A purchase requested by voice uses the same supported execution route and required approval as the corresponding text request. Preserve the user's choices when handing it off.