What problem does it solve? AI agents cannot complete purchases on a user's behalf without a secure payment credential and explicit human approval. This Skill wraps the @stripe/link-cli so an agent can authenticate with Stripe Link, create spend requests, and retrieve one-time-use virtual cards or Shared Payment Tokens — with every transaction gated by an in-app approval the agent cannot bypass. ## Core Features & Use Cases - Approval-gated spending: Every spend request pings the user's Link mobile/web app and blocks until the user approves or denies, so the agent can never self-approve a charge. - Two credential types: Issues one-time-use virtual cards for standard web checkout forms, or Shared Payment Tokens (SPT) for merchants returning HTTP 402 with method="stripe". - Secure credential handling: Card details are written to a 0600-permission file via --output-file so the PAN never enters the agent's transcript or logs. - Use Case: A user asks the agent to buy a $25 API subscription. The agent checks auth, lists payment methods, creates a spend request with line items, waits for the user's phone approval, retrieves the card to a temp file, completes checkout, and deletes the file. ## Quick Start Ask the agent to buy an item or pay for a service, for example: "Use Stripe Link to purchase a one-month subscription to this API for $20 and confirm with me before creating the spend request."
