What problem does it solve? It lets an agent pay for goods and paid APIs on the user's behalf through Stripe Link, while keeping every spend gated behind an explicit approval in the user's Link mobile or web app so the agent can never self-approve a charge. ## Core Features & Use Cases - One-time virtual cards: Creates spend requests that return single-use card credentials for standard web checkout forms and Stripe Elements. - Shared Payment Tokens (SPT): Handles merchants that respond with HTTP 402 and method="stripe" challenges via the MPP flow, decoding the raw WWW-Authenticate header and paying directly. - Approval-gated spending: Every purchase pings the Link app with --request-approval and blocks until the user approves or denies. - Secure credential handling: Retrieves card details with --output-file (0600 permissions) so the PAN never enters the agent's transcript or logs. - Use Case: A merchant API returns HTTP 402 for a paid endpoint. The skill decodes the challenge, creates a spend request, waits for the user's Link approval, and completes the payment with an SPT. ## Quick Start Ask the agent to buy an item or pay for an API call, for example: "Use Stripe Link to pay $12.99 for this checkout and ask me to approve it in the Link app."
