Design and enforce scoped payment credentials with spend controls for agent mandates using Stripe Shared Payment Tokens and OAuth-gated Link wallet authorization
Study the Shared Payment Token (SPT) specification in Stripe's documentation; SPTs are a machine-native payment credential that encode scope controls (amount ceiling, currency, merchant scope) before the token is released to an agent — the agent never sees raw card credentials
Implement the Link wallet OAuth flow: a consumer authorizes an agent by granting it OAuth access to their Link wallet, then approves each spend request through Link's web, iOS, or Android interface before any credential is released; build this approval UX into your agent's pre-purchase step
When the consumer approves, the agent obtains either a one-time-use virtual card number via Stripe Issuing for agents or an SPT; configure the SPT with the tightest scope required for the task — amount cap in the transaction currency, single merchant if possible, short expiry
Pass the SPT to the merchant's ACP or UCP checkout endpoint rather than a raw card; the merchant's payment service provider decodes and charges the SPT through Stripe, keeping PCI-sensitive data off the agent runtime
For repeat agent purchases, re-authorize a new SPT per transaction rather than reusing an old one; SPTs are designed for single-authorization use and reusing one outside its scope will result in a decline
Monitor all SPT-based transactions in the Stripe Dashboard under the Agentic Commerce section introduced in the Agentic Commerce Suite (December 2025); use the transaction metadata to correlate SPTs back to the originating agent session for reconciliation
Known gotchas
SPTs expanded in April 2026 to support network tokens (Mastercard Agent Pay, Visa Intelligent Commerce) and BNPL providers (Affirm, Klarna); if your SPT processing logic was written before this expansion, it may not handle the new SPT sub-types and will return a malformed error to agents using those payment methods
The Link OAuth consumer approval step introduces latency into otherwise autonomous agent flows; agents designed to complete purchases without any human-in-the-loop step will stall at the approval gate — communicate this constraint to consumers during agent onboarding
SPT amount caps are denominated in a specific currency at token creation time; an agent that converts between currencies before presenting the SPT may attempt to charge more than the cap in the original currency, triggering a decline
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp