stripe-link-cli

Automate Stripe Link payments via link-cli with card and SPT workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes needs to perform payments on behalf of users with strict approval flows; Stripe Link CLI is wrapped to coordinate the spend with in-app approval.

Core Features & Use Cases

  • Wraps @stripe/link-cli so Hermes can initiate purchases on behalf of a user via Stripe Link.
  • Supports card-based payments and Shared Payment Tokens (SPT) with in-app approval prompts.
  • Handles authentication flow, spend-request creation, credential retrieval, and secure handling of credential data.

Quick Start

Authenticate with Stripe Link, configure a merchant, and initiate a spend-request to obtain a secure card credential.

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 Link payments with user-approved checkout?

Stripe Link payments with user-approved checkout are automated by wrapping the official link-cli to execute purchases on behalf of users, requiring user login and approval via the Link mobile or web app to complete the transaction.

What is a Shared Payment Token and how does it work with Stripe Link?

A Shared Payment Token (SPT) is supported within Stripe Link workflows alongside card-based payments, enabling automated spend-requests that require in-app approval prompts before securely retrieving card credentials.

How do I set up the Stripe Link CLI authentication flow for automated purchases?

Setting up the Stripe Link CLI authentication flow requires installing Node.js, authenticating through the CLI, configuring a merchant, and initiating a spend-request to obtain a secure card credential output file.

Do I need Node.js to use Stripe Link CLI for automated payments?

Yes, Node.js installation is a functional prerequisite for using the Stripe Link CLI wrapper, as it is required to execute the CLI authentication flow, spend-request creation, and credential retrieval processes.

Can I use Stripe Link CLI for payments outside the United States?

No, the Stripe Link CLI wrapper applies in US-only contexts, supporting card and Shared Payment Token workflows with in-app approval prompts specifically within the United States payment infrastructure.

How does the Stripe Link CLI handle sensitive card data during automated payments?

The Stripe Link CLI handles sensitive card data by restricting data exposure through secure output files and explicitly avoiding logging any sensitive card data during the credential retrieval and spend-request processes.