stripe-link-cli

Completes purchases via Stripe Link using virtual cards and Shared Payment Tokens.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/episvr/USTB-2026-SummerInternship --skill stripe-link-cli-episvr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stripe-link-cli
Source: https://github.com/episvr/USTB-2026-SummerInternship/tree/main/hermes-config/optional-skills/payments/stripe-link-cli
Command: npx skills add https://github.com/episvr/USTB-2026-SummerInternship --skill stripe-link-cli-episvr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @stripe/link-cli.

What problem does it solve? It lets an AI agent pay for goods and services on the user's behalf through Stripe Link, while keeping every spend gated by an explicit in-app approval so the agent can never self-approve a charge. ## Core Features & Use Cases - One-time virtual cards: Create spend requests that generate single-use card credentials for standard web checkout forms, with the PAN written to a 0600-permission file instead of the agent transcript. - Shared Payment Tokens (SPT): Pay merchants that respond with HTTP 402 and method="stripe" by decoding the challenge and completing machine-to-machine payments. - Approval-gated spending: Every spend request pings the user's Link mobile/web app and blocks until the user approves or denies. - Use Case: A user asks the agent to buy a $12 API subscription. The agent checks auth, lists payment methods, creates a spend request with line items, waits for the user's Link app approval, retrieves the card to a secure file, and deletes it after checkout. ## Quick Start Ask the agent to buy an item or pay for a service, and it will log in to Link, request your approval in the Link app, and complete the checkout with a one-time-use card.

Frequently Asked Questions about stripe-link-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I let an AI agent make purchases with Stripe Link?▼

Install @stripe/link-cli globally via npm, authenticate with link-cli auth login, then create a spend request with a payment method ID, amount in cents, and line items. The --request-approval flag pings your Link app and blocks until you approve or deny.

How to pay a merchant API that returns HTTP 402 with Stripe?▼

Pass the raw WWW-Authenticate header to link-cli mpp decode to validate the challenge, then create a spend request with --credential-type shared_payment_token and complete payment via link-cli mpp pay with the spend request ID.

Does Stripe Link CLI work outside the US or on Windows?▼

No. The Link account requirement makes it US-only, and the upstream CLI does not support Windows. The skill is gated to linux and macos platforms, and auth login will fail for non-US users.

Can the agent approve its own spend requests?▼

No. Every spend is gated by an approval in the Link mobile or web app, and the agent cannot self-approve. The CLI exits non-zero if the user denies the request or the approval times out.

How are card details kept out of agent logs?▼

Retrieve credentials with --output-file so the full PAN is written to a file with 0600 permissions instead of stdout. The agent only sees redacted fields like brand, last4, and expiry, and should delete the file after the purchase.

Can Stripe Link CLI run as an MCP server?▼

Yes. Running @stripe/link-cli --mcp exposes the same commands as MCP tools over stdio, and it can be registered with hermes mcp add. The Link app approval step still applies and is not bypassed by MCP.