EDITORIAL ARTICLE
Stripe Agentic Commerce: Connecting AI Platforms and Merchants with Scoped Credentials
Project reference · Stripe ↗Type: Merchant payments, scoped credentials and issuing infrastructure. Audience: Merchants, agent platforms and app developers. Sources reviewed: October 28, 2026. No hands-on test.
When a user asks a shopping agent to buy luggage, the agent should not therefore receive the user’s full card number. Stripe’s Agentic Commerce Suite uses a Shared Payment Token (SPT) to provide scoped payment capability while connecting product, checkout, payment and risk management to the merchant. Stripe also offers developer products such as Issuing and Link Agent Wallet; these are distinct products.
Background and position
Stripe provides payment processing, checkout and card-issuing infrastructure to merchants and platforms. Agentic Commerce Suite helps businesses sell through AI channels; SPT is a payment credential within the suite, while Issuing lets businesses build card experiences. Link is a consumer payment experience and should be analyzed separately. Issuing prices cannot be applied automatically to Link users. Suite announcement · Agentic Commerce
How can a scoped shopping credential work?
An SPT can limit merchant, amount and validity while concealing underlying credentials. Stripe says it can connect payment risk signals with a transaction; actual authorization, payment and confirmation depend on the integration. Scope can reduce misuse without guaranteeing approval, delivery or an automatic refund. Stripe explanation
| Capability | Audience | What to verify |
|---|---|---|
| Agentic Commerce Suite | Merchants and AI platforms | Eligibility, channels, product data and order synchronization |
| SPT | Agent transactions needing scoped credentials | Merchant, amount, expiry and revocation; source of underlying credentials |
| Issuing | Businesses building card experiences | Issuer, regions, cardholder eligibility, limits and compliance |
| Radar | Merchants using Stripe risk tools | Data sharing, thresholds and ultimate responsibility |
| MPP | Developer and machine-payment scenarios | Payment methods, regions, billing and actual support |
Stripe’s product page also covers MPP, Link and Issuing. Its presence across shopping and machine calls does not mean every customer can immediately use every capability. Product page
Business model and differences
Stripe’s general business charges for payments, issuing and other products according to published prices or contract. Its US pricing lists a $0.10 virtual-card issuing price among baseline charges; that is neither an SPT per-transaction rate nor a Link consumer price. Confirm suite-specific prices and revenue sharing by contract.
Stripe may retain merchant payments, issuing and risk business as commerce moves into AI interfaces. This is an inference, not disclosed agent revenue. Checkout.com’s ACP API also connects AI platforms and merchants through scoped delegated credentials; compare supported merchants, platforms, methods and contract instead of assuming equivalent support from the ACP label. Visa and Stripe can occupy different layers of a card transaction; Stripe more often provides PSP, merchant and developer products.
Before implementation confirm eligibility, SPT expiry and amount scope, user confirmation, 3DS or other authentication, duplicate charges, refunds and responsibility with Stripe.
What objects exist between browsing and payment?
Imagine an $80 backpack. A consumer confirms item, shipping and final price in an agent interface; the platform obtains an SPT through a supported integration. The token can limit merchant, amount and validity, and is passed to the merchant or processor. Stripe says the agent need not see underlying consumer credentials, but the merchant still handles inventory, tax, delivery, returns and support. An SPT is neither an order nor issuer approval. Stripe explanation · Primer
| Object | Typical responsible party | States not to conflate |
|---|---|---|
| Product and cart | Merchant and AI platform | Added to cart does not mean inventory is reserved |
| SPT | Stripe and integrating platform | Created does not mean the transaction was approved |
| Card or other payment | PSP, network, issuer and others | Approval, charge and settlement are distinct |
| Fulfillment and refunds | Merchant and related services | Payment success does not mean delivery |
If final taxes put an order above the authorized SPT amount, check the API and implementation to determine whether the token can be adjusted, approval must be renewed or payment rejected. After a timeout, query the original order and payment and follow the interface’s supported idempotency mechanism; a retry is not inherently safe.
Why SPT, Issuing and MPP do not share one price table
SPT supports existing consumer payment methods in supported scenarios; Issuing helps developers build card products; MPP is a machine-payment interaction protocol. An API call may use MPP and wallet payment, an e-commerce order may use SPT, and a business may configure cards with Issuing. Contracting parties and buyer and merchant fees differ. The US $0.10 Issuing virtual-card price explains one component, not processing, funding, exchange or total payment cost. Agentic Commerce · Pricing
Stripe’s portfolio could connect agent interfaces, merchants and developers: merchants continue accepting payment, AI products gain checkout, and developers get programmable tools. This is analysis of the portfolio; without company data it does not establish agent-related volume, profit or market share. Request a complete quote for the specific merchant, country and order value.