Stripe Link (Wallet for Agents)
OAuth to Link, spend request, human approval, one-time card or shared payment token
Stripe’s Link wallet for agents (built on Issuing for agents) lets a consumer grant an agent access to Link via OAuth. The agent creates a spend request with merchant, amount, and context. The person approves in Link (web or iOS/Android). Link then returns a one-time-use card or a Shared Payment Token (SPT) — scoped with controls such as amount, currency, and merchant. The agent never receives the wallet’s raw backing credentials. Stripe’s launch post states each request currently requires review before the credential is shared, with planned expansion to standing limits. Related playbooks: Agent Payments & Spend-Policy Control Plane; Harness: Permission Outside the Agent (Muse launch partnered with Stripe Link for single-use scoped cards).
Use Cases
- OAuth-connect an agent to a consumer Link wallet
- Create a spend request the human approves in the Link app
- Complete an open-web checkout with a one-time virtual card
- Pay machine-payment / HTTP 402 merchants with a shared payment token
- Keep raw wallet credentials out of the agent context
Key Features
OAuth to Link
Register an OAuth client, send the user through Link authorization, exchange the code for an access token. The agent calls Link on the customer’s behalf.
Spend requests
Agent supplies merchant, amount, context, and credential type. Link returns an approval URL. Today, Stripe documents per-request human review.
One-time card
Default credential for open-web checkout. Stripe documents the card as one-time-use, with a validity window (docs: expires relative to spend-request creation).
Shared Payment Token (SPT)
For sellers that accept programmatic / machine-payment credentials. Stripe documents SPT as one-time-use; failed payment requires a new spend request.
No raw wallet PAN to the agent
The backing cards and bank accounts stay in Link. The agent receives only the issued one-time credential after approval.