What problem does it solve?
Stripe Link spend credentials are hard to integrate safely into agent workflows, because you need secure, one-time payment details while keeping the user in control of every transaction.
Core Features & Use Cases
- Per-transaction approval via the Link mobile app: the agent requests spend credentials and the user approves or denies each purchase from their phone, preventing standing authority.
- One-time-use payment credentials for merchants: approved spend requests return card or tokenized credentials that are valid for a single merchant + amount.
- Machine Payments Protocol (HTTP 402 / MPP) support: for MPP-capable merchants, agents can complete checkouts programmatically using shared payment tokens.
- Test mode for safe rollout: a test flag enables end-to-end verification without moving real money.
Quick Start
Use the add-link skill to wire Link into a NanoClaw agent group, then run link-cli auth login on the host and ask the agent to “Issue me a test-mode card for $1 at example.com” to verify the full approval flow.