Stripe's May 27 update widened the set of supported payment methods and tightened the controls around recurring billing. If you're building agent commerce, that's welcome — and it solves a problem you probably weren't stuck on.
Because for an agent buying something, payment is the easy part. Stripe has spent fifteen years making "accept money from anyone, anywhere, any way" a solved problem. The question a real merchant asks first isn't how the agent pays. It's whether this agent should be completing this purchase at all — and no number of new payment methods answers that.
The gap the rails don't cover
An agent shows up to check out. Four things Stripe was never designed to tell you:
- •Who's behind it:An agent isn't a person; someone operates it, and you either know who or you don't.
- •Whether they're allowed:Age, jurisdiction, category. A recurring subscription to a restricted product doesn't care that the card cleared.
- •Whether they're clean:OFAC and sanctions screening on the operator and the settling wallet.
- •Whether you can prove it:The recurring-billing controls Stripe just improved will happily re-charge a card every month. To whom, and on whose authority, is your problem to answer.
Payment succeeding and a purchase being allowed are two different events. Stripe confirms the first. The second is identity, and it has to happen before the charge.
Where the decision lives
One assessment in front of the checkout route, before the Stripe charge:
1const result = await agentscore.assess(walletAddress, { policy });
2// policy = { require_kyc, require_sanctions_clear, min_age, allowed_jurisdictions }
3
4if (result.decision === 'deny') {
5 return res.status(403).json({
6 error: 'compliance_denied',
7 reasons: result.decision_reasons,
8 verify_url: result.verify_url,
9 });
10}
11// decision === 'allow' → hand off to Stripe to actually collect the moneyA subscription, gated
An agent signs its principal up for a monthly plan. Before Stripe ever creates the recurring charge, `assess` checks the operator: verified, sanctions-clear, in an allowed jurisdiction → `allow`, and the subscription starts. Fail any check and it's a `403` with a `verify_url` instead of a subscription you'd have to unwind later — which, with recurring billing, means unwinding every month you missed it.
The point
Stripe keeps making it easier to get paid. That's real, and the May 27 update is more of it. But the harder half of agent commerce is deciding whether to say yes to the agent doing the paying — and that's the layer we sit in, one call before the charge.
Building agent checkout on Stripe?
See the identity gateReady to power your agents with secure commerce?
Join innovators using AgentScore to accept payments, verify buyers, and ensure compliance for every AI-driven transaction.
Read More Blog Posts
Coinbase CDP Hardens Embedded Wallets With Attestation
Coinbase Developer Platform shipped a meaningful security update to its Embedded Wallets product: iOS App Attest and Android Play Integrity support, combined wi
Coinbase CDP CLI Brings Terminal-First Agent Signing and Wallet Delegation
Coinbase released CLI tooling and MCP server support to simplify how developers integrate onchain wallets into autonomous systems. 22 words. Engineers can now a