@visa/cli 5.0.0-rc.337 → 5.0.0-rc.339

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -370,16 +370,18 @@ BEFORE it is signed), then `wallet_pay`. The served wallet tools are `wallet_dis
370
370
  address + faucet), and `wallet_export` (export key material — dangerous). All spending is
371
371
  gated by the owner-approved local policy caps.
372
372
 
373
- Card: not available in this build. Visa CLI ships no browser checkout (#8940), so
374
- `start_card_mandate` returns `card_browser_checkout_removed` and creates no mandate, and
375
- every `pay_merchant` action refuses with the same code. Nothing is charged. Do not offer
376
- card checkout to the user, and do not relay a card approval URL; the wallet rail above is
377
- the payment path where the merchant supports it. A saved card, grant or tester flag does
378
- not enable card payment, and another enrollment will not repair it. UCP discovery and
379
- checkout preparation are not payment execution. A continuable `ucp_checkout_handoff`
380
- returns safe facts and `not_ready` / `card_browser_checkout_removed`, without a payment
381
- request or continuation capability URL. Preserve the existing checkout for the owner
382
- to continue with the merchant; use `ucp_checkout_reconcile` afterward to check completion.
373
+ Card: Visa-operated browser checkout is retired; another enrollment will not repair it.
374
+ `start_card_mandate` and `pay_merchant` refuse with `card_browser_checkout_removed`.
375
+ On local builds that list `purchase_create`,
376
+ `purchase_retrieve` and `purchase_cancel`, the protected card preview uses the
377
+ host's checkout tools and the existing eligible card and agent identity. Follow
378
+ `next`: relay the single owner setup or limits URL, let the owner act, then repeat
379
+ the same purchase call. Never ask for funding-card secrets in chat. Explicit
380
+ `include:"card"` may put the issued purchase credential in model/chat history,
381
+ under the owner's disclosure consent. A saved card or tester flag alone does
382
+ not establish eligibility or merchant credential compatibility. UCP discovery
383
+ and preparation remain separate from payment execution; a `not_ready` handoff
384
+ is not permission to pay or to revive the retired browser flow.
383
385
 
384
386
  On a hosted runtime, **every payment requires the owner's browser
385
387
  approval** until the protected no-tap executor lands. Enrollment, a session, or a spending
@@ -418,8 +420,15 @@ org-wide AgentMail key off the runtime — provisioning happens only through
418
420
 
419
421
  ## Optional checkout profile (separate from setup)
420
422
 
421
- Do not collect a checkout profile to repair `pay_merchant`: card payment is unavailable
422
- even with a profile, card authority and `checkout_agent_access`. Existing
423
+ Do not collect a checkout profile to repair `pay_merchant`: Visa browser checkout
424
+ is retired. On local builds that list `purchase_create`, `purchase_retrieve` and
425
+ `purchase_cancel`, the protected card preview reuses this identity and verified
426
+ card. The host supplies checkout and billing details, owns browser submission,
427
+ and follows the returned `next` action. Fixed protocol fields and `requestKey`
428
+ may be omitted; retain the same checkout reference and terms on retry. Explicit
429
+ `include:"card"` returns issued purchase credentials under owner consent and may
430
+ put them in model/chat history. Never request original funding-card details in
431
+ chat, bypass eligibility, or retry an uncertain merchant submission. Existing
423
432
  `~/.visa-mcp/contact.json` files use the format below; preserve them with mode `0600`.
424
433
  Never infer or invent identity or address data.
425
434
 
@@ -1,18 +1,26 @@
1
1
  ---
2
2
  name: visa-shopify-checkout
3
- description: Prepare an exact Shopify checkout with UCP and reconcile a merchant order. Visa card payment is unavailable in this build; preserve the checkout for the owner to continue with the merchant. Use for authorized checkout preparation or reconciliation, without claiming payment support.
3
+ description: Prepare an exact Shopify checkout with UCP and reconcile a merchant order. Payment through the retired Visa browser tools is unavailable; preserve the checkout for the owner to continue with the merchant. Use for authorized checkout preparation or reconciliation, without claiming payment support from those tools.
4
4
  allowed-tools: Bash(visa:*) Bash(visa-cli:*)
5
5
  metadata:
6
6
  author: visa
7
7
  version: '0.1.0'
8
8
  ---
9
9
 
10
+ **Protected card preview:** this skill describes the retired Shopify execution lane.
11
+ Its unavailability does not describe protected device `purchase_create`,
12
+ `purchase_retrieve`, and `purchase_cancel`. For that preview, follow
13
+ `pair-visa-agent`: the host owns browsing and checkout, and must relay the one
14
+ owner setup/limits URL the tool returns. Credentials require explicit retrieval
15
+ and owner disclosure consent. A checkout confirmation is host observation, not
16
+ verified settlement. Never restart a payment to recover an uncertain result.
17
+
10
18
  # Visa Shopify checkout
11
19
 
12
20
  This skill supports the preview/RC checkout surface only. It prepares and inspects
13
- merchant checkouts and reconciles their outcomes. Visa card payment is unavailable:
21
+ merchant checkouts and reconciles their outcomes. The retired Visa browser-payment tools are unavailable:
14
22
  `pay_merchant` and `start_card_mandate` refuse with `card_browser_checkout_removed`.
15
- A saved card, grant, tester flag or another enrollment will not enable payment.
23
+ For those retired tools, a saved card, grant, tester flag or another enrollment will not enable payment.
16
24
  Do not offer the removed `visa checkout` command or a Visa browser fallback.
17
25
 
18
26
  The host agent owns shopping and browser interaction. Discovery is optional:
@@ -23,7 +31,7 @@ accept an exact merchant/product supplied by the host or selected through
23
31
 
24
32
  Before creating a checkout, pin the exact merchant, product, variant, quantity,
25
33
  currency, maximum all-in amount including tax and shipping, and authorized
26
- fulfillment details. Explain that this build cannot pay with a Visa card before
34
+ fulfillment details. Establish whether the host supports the protected device preview described above before
27
35
  asking the user to invest in checkout setup. Do not collect a card, grant, mandate
28
36
  or contact profile to repair unavailable payment. Inspect unresolved activity
29
37
  before starting another checkout for the same purchase.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@visa/cli",
3
- "version": "5.0.0-rc.337",
3
+ "version": "5.0.0-rc.339",
4
4
  "description": "Visa CLI runtime for stable agent identity and separately authorized payment capabilities",
5
5
  "bin": {
6
6
  "visa-cli": "./bin/visa-cli.js",
package/server.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
3
3
  "name": "io.github.visa-crypto-labs/visa-cli",
4
- "version": "5.0.0-rc.337",
4
+ "version": "5.0.0-rc.339",
5
5
  "title": "Visa CLI",
6
6
  "description": "Pair a human-approved agent identity, configure payment capabilities separately, and discover and pay x402 services from your AI coding assistant.",
7
7
  "websiteUrl": "https://github.com/Visa-Crypto-Labs/Visa-mono/tree/main/packages/cli#readme",
@@ -9,7 +9,7 @@
9
9
  {
10
10
  "registryType": "npm",
11
11
  "identifier": "@visa/cli",
12
- "version": "5.0.0-rc.337",
12
+ "version": "5.0.0-rc.339",
13
13
  "transport": {
14
14
  "type": "stdio"
15
15
  },