Skip to content
Logo

Overview

Link, a digital wallet built by Stripe, gives agents a secure way to pay on a customer’s behalf without exposing or storing the customer’s real card details. An agent creates a spend request, which is a record of what it wants to buy, from which seller, for how much, and why. The customer approves the request, and Link returns a scoped payment credential for checkout. You can use Link CLI for ready-made workflows or an SDK to build your own payments integration.

What you can build

Use caseWhat your agent doesExample
Agent paymentsCreates a spend request for a specific purchase. The customer approves it, and Link returns a payment credential the agent uses to pay. By default the credential is for a single use; a request can instead set a recurring spending limit.“Buy me this book from Stripe Press”
Financial insightsReads transactions, balances, and account details from the accounts the customer chooses to share.“What did I spend on dining this month?”
Agent identity (beta)Proves to a website or API that Link vouches for it, or shares claims that Link signed, such as a verified email. Services check these credentials with the Agent Identity SDK.“Register me for the Autumn meetup with my email”

One integration can use any combination of these capabilities. Payments and financial insights depend on the scopes you request.

How it works

  1. The customer connects their Link account to an agent or application.
  2. The agent describes the seller, amount, and reason for the purchase.
  3. Link presents those details to the customer for approval.
  4. After approval, Link issues a credential for the agent to complete checkout.

The customer remains in control of the purchase while the agent handles the checkout mechanics.

Payment credentials

Choose a payment option based on how the seller accepts payment. Spend requests support three credential_type values: card for a virtual card, shared_payment_token for a Shared Payment Token, and link_pay_token for a Link Pay Token.

Virtual card

A virtual card, one-time-use unless the request sets recurring terms, works with a standard web checkout form. It isn’t limited to Link-enabled sellers or sellers that use Stripe.

Shared Payment Token

A Shared Payment Token (SPT) works when a seller accepts programmatic payments through Machine Payments Protocol (MPP).

A Link Pay Token (LPT) works on Stripe-hosted checkouts that support Link. The agent injects the token into the checkout page, and it also fills in billing and shipping details.

Link CLI and the Link SDKs call the Link API at api.link.com and authorizes against login.link.com. These are separate from the Stripe API at api.stripe.com. You authenticate with an OAuth access token that represents one customer, not with a Stripe API key, and the Stripe server-side SDKs don’t cover these endpoints. Use Link CLI, a Link SDK, or plain HTTP requests.

Ways to integrate

Use Link CLI for interactive commands, agent skills, structured output, or a local Model Context Protocol (MCP) server.

npx @stripe/link-cli onboard

Quickstart

SDKs

The Link SDKs provide typed API resources for building custom payment integrations. Your application supplies and manages the access token. The SDKs don’t perform login or persist credentials.

Choose a language, then follow its installation and client setup instructions: TypeScript, Go, or Python.

All three SDKs require your application to supply an access token and manage authorization. For a hosted application, follow the OAuth reference.