Qianwen Payment

Qwen AI Platform Payment

Qwen AI Platform (千问AI平台) cash balance, fixed-amount Alipay recharge, and new Token Plan purchase orchestration. Use this Skill only for a Qwen AI Platform account. Do not infer recharge intent or an overdue account from a low balance, a generic quota error, HTTP status, or unrelated model failure.

Recharge and Token Plan are isolated domains. Recharge uses only the original recharge references and scripts listed below. Token Plan uses only its explicitly listed Token Plan files, plus the unchanged generic command-resolver.mjs. Never use one domain's validator, poller, recovery state, or user-facing result wording in the other domain.

Compatibility and resources

Requires Node 18.18+ for every route in this Skill. Recharge uses scripts/preflight.mjs; Token Plan uses scripts/tokenplan-preflight.mjs. Each domain script exclusively owns its runtime baseline, QianWen CLI compatibility, validation, and Alipay path decisions; do not reproduce or override those decisions in prose.

Load references only when the current route needs their authoritative detail. For fixed-amount recharge, read recharge-flow.md only after the user confirms order creation. Also read its recovery section when the user explicitly reports that the current order's QR was not displayed and the current order's Alipay materials are still retained. For a Token Plan quote, purchase, or existing-purchase follow-up, load tokenplan-flow.md; do not load Recharge references.

Routes

Recharge core rules

1. Localize only QianWen-owned output. Follow the language of the user's latest substantive message. The AI risk notice may be translated in full. Only user-facing Alipay content is passed through verbatim; route-specific control data is never user-facing.
2. One confirmation, one create attempt. Confirm the exact masked account, normalized amount, Alipay method, and operation scope. A confirmation authorizes exactly one invocation of the create command and is consumed before that invocation. It cannot authorize another order, including in the same conversation with the same account and amount or for a retry, replacement, or additional order. A status query, QR recovery, payment continuation, or statement that payment was completed never authorizes creation. Never automatically retry an interrupted, malformed, timed-out, nonzero, or otherwise unconfirmed create attempt.
3. One payment owner within an outer recharge lifecycle. This Skill owns order creation, payment handoff, and the decision to query the QianWen result. Preflight selects direct or alipay-payment-skill before order creation. alipay-payment-skill owns safety, commands, retries, output, and stop decisions only within the delegated payment-side step. Never switch paths after a direct Alipay command has started because its side effects may be unknown.
4. No payment improvisation. Use only the unchanged, validated paymentUrl from the current create response. Never accept, rewrite, reconstruct, normalize, decode/re-encode, or substitute a link from the user, history, logs, or another order.
5. One proof of credit. Only the shared recharge-result classifier returning category=credited proves the recharge was credited. An Alipay result, QR scan, user statement, balance change, or history entry does not.
6. Protect credentials and transaction data. Never request an Alipay password, bank-card number, SMS code, API key, cookie, or pasted token. Keep full account identifiers, order IDs, payment links, and raw payloads only in current-flow memory. Do not copy them to files, logs, long-term memory, or sub-agent messages.
7. Deliver before polling. Complete Progress node 2 before any result query or poll-recharge.mjs. A command result visible only to the Agent, file read, preview, draft, or planned final reply is not delivery.
8. Polling route. Use recharge-flow.md for polling eligibility and business sequencing.
9. Consistent execution context. Apply the execution-context and authentication-recovery contract in cli-contracts.md to QianWen commands.

Recharge direct-path sessionId resolution

This section applies only to the direct path. The delegated path follows alipay-payment-skill. sessionId is optional and applies only to alipay-bot submit-payment; trigger-payment-signal never receives it. Use the first non-empty value from this order:

Use the value as-is. Do not generate one, ask the user for one, or substitute another business ID. If all sources are empty, omit --session-id.

Recharge pre-confirmation fast path

1. Amount

Use only the amount intentionally supplied for the current recharge.

• Convert yuan, jiao/mao, and fen exactly with decimal-string or integer arithmetic.
• Continue only when the amount is unambiguous, positive, denominated in CNY, and exactly representable in cents.
• Ask for one exact amount when it is missing, approximate, a range, contains multiple candidates, uses another currency, or has sub-cent precision.
• Never guess, round, truncate, or reuse an amount from another request.

Validate the normalized amount together with route dependencies:

node <skill-dir>/scripts/preflight.mjs --route recharge-order --amount <normalized>

For every recharge-order attempt, the compatible Alipay CLI and alipay-payment-skill are independent blocking dependencies. Preflight validates the CLI contract; separately verify that alipay-payment-skill is present and loadable in the host's available-Skill registry. Neither dependency substitutes for the other, even when preflight selects payment_path=direct. Complete both checks before authentication, confirmation, or order creation.

After both dependency gates pass, retain the returned payment_path. direct means the optional pre-handoff signal capability is available; alipay-payment-skill means payment submission must use the already-verified alipay-payment-skill. If either dependency is unavailable, stop and use cli-contracts.md § Dependency setup only when installation guidance is needed.

2. Authentication and account snapshot

Verify a server-authenticated QianWen CLI account using the authentication contract in cli-contracts.md. Use only the CLI OAuth device flow; show only its returned verification URL and never ask for credentials or tokens.

Retain the full account identifier only for current-flow consistency checks and show only its masked form. Immediately before creation, re-read the authenticated account and compare it with the confirmed snapshot. Any account, amount, currency, payment-method, or operation-scope change invalidates the confirmation.

Do not query balance, recharge history, or prior orders before creation. They add latency without protecting this transaction.

3. Confirmation

For every fresh fixed-amount create confirmation, the first visible line must be this complete AI risk notice, localized when appropriate:

AI risk notice: This recharge request was prepared by AI and may not reflect your actual intent. Review the amount, account, and operation scope; do not confirm if anything is incorrect.

Then show the masked account, normalized amount, Alipay method, and that confirmation creates one recharge order and enters the payment flow. End with a natural confirmation question. Do not use a mechanical Confirm/Cancel option list.

• Affirmative: recheck the account and normalized amount, consume the confirmation, then read and execute recharge-flow.md.
• Negative: run nothing and output the localized equivalent of Recharge canceled.
• Material change: show a new confirmation block with the risk notice.

Recharge user-visible progress

Communicate only these business transitions. Do not expose CLI commands, arguments, skill routing, validators, service names, polling internals, sessionId, the internal polling deadline, or raw QianWen-side errors unless the user explicitly asks for troubleshooting information.