Agent Payments & Spend-Policy Control Plane
Enroll a card, cap the mandate, hand the agent a payment capability — not the PAN
Operator recipe for letting an agent buy mid-task without giving it a raw unbounded card. Enroll and tokenize the card once, attach a spend policy (cap, clock, merchant/API scope), issue a scoped payment capability, allow x402-style mid-task purchases inside that mandate, then revoke. Pair the payment plane with Know-Your-Agent identity (Ant International, Mastercard, and Visa interoperability work is in progress as of 2026-09-10 — not a finished shared standard) and with credential Connections that distinguish agent-owned vs caller-owned secrets. Primaries: Nevermined Pay; LangChain “Agents That Pay”; PR Newswire KYA collaboration; LangChain Connections. Related catalog tools: Nevermined, LangChain Managed Deep Agents, Stripe Link (Wallet for Agents).
Core Workflows (6)
Each workflow represents a critical business function. Click any workflow to see detailed automation architecture.
Enroll and tokenize the card
Led by: Enrollment OperatorHuman enrolls a credit or debit card once. The PAN is tokenized in a PCI-compliant vault (Nevermined documents Stripe, Braintree, or Visa Intelligent Commerce). The operator never hands the raw card number to the agent.
Attach a capped spend mandate
Led by: Spend-Policy OperatorSet the policy before any buy: total budget, time window that auto-stops, optional per-purchase cap, optional transaction count, optional merchant/API-key restriction. Enforcement is server-side before settlement. A raw unbounded payment method makes the spend answer “everything”; a delegation makes it a cap, a clock, and an off switch.
Issue a payment capability, not the card
Led by: Capability IssuerThe agent receives a scoped credential — a payment capability / virtual-card credential encoding identity, limits, and restrictions — not the enrolled PAN. One capability can be reused across sessions, tools, and frameworks until the mandate expires or is revoked.
Mid-task buy (x402-style)
Led by: Paying AgentWhen the agent hits a paid API or tool, it presents the payment token (x402 / payment header) and settles inside the mandate. LangChain’s Nevermined cookbook shows mid-task purchase and top-up of search credits without a human in the loop for each in-mandate buy; out-of-policy amounts pause. This is the same pattern Stripe Link uses for a one-time card or shared payment token after a spend request — different vendor, same “capability not PAN” rule.
Pair KYA identity and credential Connections
Led by: Identity OperatorKYA: Ant International, Mastercard, and Visa announced collaboration on a Know-Your-Agent interoperability framework (2026-09-10) so networks can recognize agents across ecosystems while keeping their own verification. Treat that as interop in progress, not a live shared cert. Connections: LangChain Managed Deep Agents stores named credentials as agent-owned (shared by every caller) or caller/user-owned (resolved per person at runtime). Decide ownership when creating the connection; it does not change later. Pair the spend mandate with the matching identity and credential owner.
Revoke the mandate
Led by: Spend-Policy OperatorRevoke or let the clock expire. After revoke, the agent still exists but the payment capability stops. Rotate or revoke Connections in the workspace without shipping a new PAN to the agent.