How shared payment tokens work In Stripe’s vision of agentic commerce, a consumer’s payment credentials should never pass through the agent itself. A shared payment token (SPT) is a credential that passes merchant-ward — from the consumer’s wallet toward the merchant — without the agent ever seeing the underlying payment details[^90e39a1e-87e8-5b3f-b9f2-f003e83fd62b@3139]. Emily Glassberg Sands groups SPTs with Stripe’s Agent Commerce Protocol and its Link wallet as the payment infrastructure being rebuilt so agents can transact[^90e39a1e-87e8-5b3f-b9f2-f003e83fd62b@2760]. The Link wallet complements SPTs by letting consumers decide which agents may request credentials and under what limits[^90e39a1e-87e8-5b3f-b9f2-f003e83fd62b@3139]. Why it matters Agents are becoming a new class of internet actor, forcing identity, payments, and fraud layers to be rethought[^90e39a1e-87e8-5b3f-b9f2-f003e83fd62b@96]. SPTs are Stripe’s answer on the payment side: they keep the human cardholder in control while still letting an agent complete a purchase on their behalf. - An SPT carries payment credentials merchant-ward without exposing them to the agent. - It is part of Stripe’s Agent Commerce Protocol work with OpenAI[^90e39a1e-87e8-5b3f-b9f2-f003e83fd62b@2760]. - Stripe’s Link wallet lets consumers set which agents can request credentials and under what limits[^90e39a1e-87e8-5b3f-b9f2-f003e83fd62b@3139].