stripe-link-cli

Manage Stripe Link payments and Shared Payment Tokens via CLI.

Updated May 4, 2026
One-click install
npx skills add https://github.com/InverterNetwork/hermes-agent --skill stripe-link-cli-inverternetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-link-cli
Source: https://github.com/InverterNetwork/hermes-agent/tree/main/optional-skills/payments/stripe-link-cli
Command: npx skills add https://github.com/InverterNetwork/hermes-agent --skill stripe-link-cli-inverternetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @stripe/link-cli.

What problem does it solve?

This skill enables the agent to securely complete purchases and handle payment requests on the user's behalf without exposing sensitive card data to the agent's context.

Core Features & Use Cases

  • Secure Checkout: Executes payments using one-time-use virtual cards or Shared Payment Tokens (SPT) with mandatory user approval via the Link app.
  • Merchant Evaluation: Automatically determines the correct credential type (card vs. SPT) based on merchant requirements and HTTP 402 challenges.
  • Use Case: When a user needs to pay for a service or product, the agent uses this skill to initiate a spend request, wait for the user's mobile approval, and finalize the transaction securely.

Quick Start

Ask the agent to pay for a specific purchase using the stripe-link-cli skill after confirming the merchant details and total amount.

Frequently Asked Questions about stripe-link-cli

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

FAQPage Schema
How do I automate Stripe payments without exposing credit card details to an agent?

Automate Stripe payments securely by using the Stripe Link CLI to execute transactions via one-time-use virtual cards or Shared Payment Tokens. This requires mandatory user approval through the Link app, ensuring sensitive card data never enters the agent's context.

What is a Shared Payment Token and when is it needed for web checkout automation?

A Shared Payment Token (SPT) is a secure credential type used for web checkout automation when merchants require tokenized payments. The agent automatically determines whether to use an SPT or a virtual card by evaluating merchant requirements and HTTP 402 payment challenges.

How do I handle HTTP 402 payment challenges for automated checkouts?

Handle HTTP 402 payment challenges by allowing the agent to evaluate the response and automatically determine the correct credential type. The agent initiates a spend request using the Stripe Link CLI and waits for the user's mobile approval to finalize the transaction.

Do I need Node.js to use the Stripe Link CLI for agent-driven transactions?

Yes, you need Node.js 20+ and the @stripe/link-cli package to use the Stripe Link CLI for agent-driven transactions. The environment must also be US-based to handle web checkouts and Shared Payment Token requests for authenticated users.

Can I use Stripe Link for automated merchant payments outside the US?

No, Stripe Link for automated merchant payments currently operates within US-based environments only. It handles web checkouts and Shared Payment Token requests for authenticated users, limiting its use for international payment automation.

Why does the agent wait for mobile approval during a Stripe checkout?

The agent waits for mobile approval during a Stripe checkout to enforce secure financial transactions. Mandatory user approval via the Link app ensures that the user explicitly authorizes the spend request before any payment is finalized.