Your pricing page assumes a human clicks Subscribe. As of this month, the thing clicking might be Meta's Muse, and the card behind it lives in Stripe's Link wallet. That changes less about your billing code than the headlines suggest — and much more about one specific field than anyone is saying out loud.
1. What actually shipped, and when
Stripe launched Link's wallet for agents on 29 April 2026, built on a new Issuing for agents API. Both are generally available. The distribution arrived later: Payments Dive reported on 18 September 2026 that Meta added Link to its Muse personal agent in an 8 September announcement, following August integrations with xAI's Grok and with Instinct, a texting-based assistant from Spear Street Technology. Payments Dive puts Link at roughly 1 million merchants and 300 million users — those are the reporter's figures, not numbers Stripe published.
Spending limits, approval automation, agentic tokens and stablecoins are all still listed as coming soon, with no dates attached.
2. The credential is a single charge, not a customer
On the seller side, an agent grants you a shared payment token (SPT) scoped to your Stripe profile. You confirm a PaymentIntent with payment_method_data[shared_payment_granted_token]. Stripe then clones a fresh PaymentMethod from the customer's original, so refunds and reporting behave exactly as they would for a card you collected yourself.
The scope is deliberately narrow. usage_limits carries currency, max_amount and expires_at — and the docs state the agent sets max_amount to match the total of that one transaction. You get a single webhook, shared_payment.granted_token.deactivated, which fires when the token is consumed, expires, or is revoked. Retrieving a granted token still requires the preview header Stripe-Version: 2026-04-22.preview, and using SPTs at all means accepting Stripe's agentic commerce seller terms, which are themselves marked preview.
3. setup_future_usage has exactly one value
This is the part that matters if you bill monthly. SharedPaymentIssuedToken does carry a setup_future_usage field — but it is set by the party issuing the token, not by you, and today the only documented enum value is on_session: reuse the payment method when the customer is present in the checkout flow.
There is no off_session. Read plainly, that means an SPT is not a documented route to charging a renewal at 3am with nobody watching. An agent can buy from you. Whether it can enrol its human in something that charges again next month is not a thing Stripe's docs currently promise, and I could not find a published SPT-to-Subscription path. Treat any roadmap that leans on it as unconfirmed.
4. The seller integration is feeds, not a checkout page
Selling through agents with the Agentic Commerce Suite means uploading a CSV catalog feed and refreshing inventory and pricing roughly every 15 minutes, because a mismatch between the quoted price and the charged price fails the checkout outright. Orders then arrive as ordinary checkout.session.completed events, tagged with the originating agent in the Dashboard. The agent_details field on the PaymentIntent — exactly the thing you want for attribution — is still private preview. Availability is the US, Canada and 32 European countries.
If you sell an API rather than a product, that is a separate track: machine payments over MPP or x402.
Ask, don't assume
The honest answer to "can a bot subscribe to us?" is a docs question, a scope question and a dates question all at once — and it moves month to month. That is the job Agent Billy does: you ask what your billing actually permits right now, and the answer comes from your Stripe account rather than from a launch post.