stripe-link-cli

Request one-time payment credentials from Link wallets for agent-driven purchases.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/devtools-skills --skill stripe-link-cli-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stripe-link-cli
Source: https://github.com/reason-machines/devtools-skills/tree/main/skills/stripe-link-cli
Command: npx skills add https://github.com/reason-machines/devtools-skills --skill stripe-link-cli-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @stripe/link-cli.

What problem does it solve? AI agents cannot safely complete purchases on a user's behalf without exposing real card details. This Skill lets agents request secure, one-time-use payment credentials from a Link wallet, with every purchase approved by the user through the Link mobile app. ## Core Features & Use Cases - Spend Requests: Create payment credential requests tied to a specific merchant, amount, line items, and context, then poll for user approval. - Virtual Cards & Shared Payment Tokens: Produce virtual card (PAN) credentials for standard web checkouts or Shared Payment Tokens for Machine Payment Protocol (MPP) merchants. - Secure Credential Handling: Write full card details to 0600-permission files while stdout shows only redacted data, plus test mode for development. - Use Case: An agent shopping assistant lists the user's saved payment methods, creates a spend request for a $35 book purchase, polls until the user approves in the Link app, retrieves the virtual card, and fills the merchant checkout form. ## Quick Start Install the CLI with npm i -g @stripe/link-cli, run link-cli auth login to connect a Link account, then ask the agent to create a spend request for your purchase and approve it in the Link app.

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 a purchase with Stripe Link?▼

Authenticate with link-cli auth login, list payment methods, then create a spend request with merchant name, URL, context, amount, and line items. The user approves in the Link mobile app, and the agent retrieves a one-time virtual card or Shared Payment Token.

What is the difference between virtual card and shared payment token in Link CLI?▼

Virtual cards provide PAN credentials (number, CVC, expiry) for standard web checkout forms. Shared Payment Tokens are used with Machine Payment Protocol merchants via the link-cli mpp pay command and are one-time-use.

Can I test Link CLI spend requests without a real card?▼

Yes, pass the --test flag with payment-method-id pm_test_card when creating a spend request. This generates test credentials without touching real payment methods, useful for verifying integrations before going live.

Why does my spend request fail with context too short?▼

The --context field requires at least 100 characters describing the purchase in detail. Write a full sentence explaining what is being bought, from which merchant, and why, then retry the create command.

What is the maximum amount for a Link CLI spend request?▼

Each spend request is limited to 50000 cents ($500). For larger purchases, split the transaction into multiple spend requests or handle the payment outside Link CLI.

How do I keep full card details out of agent logs?▼

Use --output-file when retrieving a spend request with --include card. The full card is written to a file with 0600 permissions while stdout shows only redacted data like brand, last4, and expiry.