Table of Contents
Stripe Machine payments let AI agents pay-per-call over MPP and/or x402, with settled funds landing in your Stripe balance instead of a self-custody receive address.
As of September 2026 Stripe docs, the x402 Node guide prices $0.01 USDC per request to /paid on Base (eip155:8453), records each settle as a PaymentIntent with transaction_verification, and requires Stripe-Version 2026-05-27.preview.
This guide walks enablement, the HTTP 402 → Base deposit address → CDP facilitator → PaymentIntent path, network contracts, and when to stay on raw x402 or Checkout Crypto instead.
For human Checkout Crypto, see how to accept stablecoin payments on Stripe. For protocol-level accept without Stripe, see how to accept x402 USDC payments from AI agents.
Key Takeaways
- Enable Stablecoins and Crypto in Dashboard; US machine stablecoin rails exclude New York.
- x402 returns HTTP 402 with payment requirements plus a Stripe Base deposit address.
- Docs example charges $0.01 USDC per /paid request on Base (eip155:8453).
- Create deposit addresses via POST /v1/crypto/deposit_addresses with Stripe-Version 2026-05-27.preview.
- Mainnet x402 settles through Coinbase Developer Platform facilitator keys; stablecoin floor is $0.01 vs $0.50 cards/SPTs.
What Stripe Machine x402 actually is
Machine payments remove human checkout so agents can buy API calls programmatically. Your server returns a payment challenge; the agent presents a credential; Stripe settles to your Stripe balance with the usual reporting and refunds surface.
Stripe supports MPP (cards via Shared Payment Tokens plus stablecoins) and stablecoin-only x402. As of September 2026 docs, x402 USDC on Stripe is on Base; MPP lists Tempo USDC.e and Solana USDC for stablecoins.
x402 lifecycle in Stripe's guide: client hits a paid resource → server returns HTTP 402 with payment requirements and a Stripe deposit address → client pays USDC and retries with authorization → facilitator settles on-chain → server creates a PaymentIntent with transaction_verification → server returns the resource.
Who this is for (and who should skip it)
Use Stripe Machine x402 when agents must pay per HTTP call in USDC, you want PaymentIntents and Stripe balance reconciliation, and your business is in a US state other than New York (or you have emailed machine-payments@stripe.com for 30+ country access).
Skip it when callers are humans on Checkout, you need New York coverage today, you refuse a CDP facilitator dependency, or you want a self-custody payTo without Stripe recording. Those jobs map to Checkout Crypto, raw x402 accept, or Circle Agent Nanopayments.
Enable Stablecoins and Crypto for machine payments
In Stripe Dashboard Payment methods, request the Stablecoins and Crypto method. Stripe reviews the request (it can stay Pending) and contacts you if more detail is needed.
If you want crypto only on machine traffic, create a separate payment method configuration dedicated to machine payments. Outside the US, email machine-payments@stripe.com with your Stripe account ID to request stablecoin machine payments in 30+ countries.
Microtransaction floors from the Machine payments overview: cards/SPTs minimum $0.50; stablecoins minimum $0.01 USDC. That $0.01 floor is why agent pay-per-call fits stablecoin rails better than SPT card grants.
Create a Base deposit address and CDP facilitator keys
Before the server middleware, create a crypto deposit address with POST /v1/crypto/deposit_addresses, network=base, and header Stripe-Version: 2026-05-27.preview (the version cited on Stripe's x402 page as of September 2026).
Store the returned address as DEPOSIT_ADDRESS. Stripe says you can create addresses often, but keep those calls off the hot request path.
Mainnet x402 settlement on Stripe's guide goes through the Coinbase Developer Platform (CDP) facilitator. Sign up for CDP, create API keys, and pass CDP_API_KEY_ID / CDP_API_KEY_SECRET into createFacilitatorConfig. See CDP running on mainnet and how to choose an x402 facilitator for USDC.
Wire the x402 endpoint (docs $0.01 Base example)
Stripe's Node sample installs @x402/core, @x402/evm, @x402/hono, @coinbase/x402, Hono, and Stripe, then registers eip155:8453 with ExactEvmScheme.
paymentMiddleware prices GET /paid at "$0.01" on eip155:8453 with payTo set to the lowercase deposit address. A bare curl without payment should return HTTP 402 with a payment-required header.
After facilitator settle, onAfterSettle creates a PaymentIntent with payment_method_data.type: crypto, mode: transaction_verification, network base, and the on-chain transaction_hash, using the tx hash as the idempotency key.
Because the deposit address is live-mode, Stripe's test path with purl moves real funds. Start with the docs $0.01 example, then confirm the PaymentIntent in Dashboard Payments.
transaction_verification networks and USDC contracts
PaymentIntents with crypto transaction_verification support USDC on the networks Stripe lists as of September 2026:
| Network | Token | Token contract (Stripe docs) |
|---|---|---|
| Tempo | USDC | 0x20c000000000000000000000b9537d11c60e8b50 |
| Base | USDC | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| Solana | USDC | EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v |
The x402 guide's sample path is Base. Match network in transaction_verification_options to the chain you actually settled, character for character against Circle's published contract for that network.
Machine x402 vs Checkout Crypto vs raw x402
| Dimension | Stripe Machine x402 | Stripe Checkout Crypto | Raw x402 / Circle path |
|---|---|---|---|
| Caller | AI agents (HTTP) | Humans (Checkout / Elements) | Agents (protocol / CLI) |
| Fee / price model | You set resource price (docs $0.01 example) | 1.5% of USD amount | Facilitator / Gateway rules |
| Floor | $0.01 USDC (stablecoin machine) | Ticket under $10k per tx | Circle nanopay floors can be far lower |
| Settle | Stripe balance + PaymentIntent | Stripe balance via Crypto method | Self-custody or Circle Gateway |
| US availability note | All US states except New York | US live; EU/HK/MX/CH private preview | Depends on your stack |
| Facilitator | CDP keys required for mainnet sample | Hosted crypto.stripe.com | You choose facilitator |
Primary sources: Stripe x402 payments, Stripe Machine payments, and the SCI Checkout Crypto guide linked above.
Operational pitfalls
Shipping from New York. Stripe's stablecoin machine availability excludes NY. Confirm entity location before promising US national coverage.
Skipping Crypto access review. The method stays Pending until Stripe approves. A greyed toggle is eligibility, not a Hono bug.
Testing mainnet deposit addresses with play money assumptions. Live-mode addresses and purl tests move real USDC. Cap the first settle at the docs $0.01 example.
Wrong network on transaction_verification. Base settle recorded as Solana (or the reverse) fails verification. Pin network and contract from the Stripe table.
Confusing Machine x402 with Checkout Crypto. Agents on HTTP 402 are not humans on crypto.stripe.com. Pricing, floors, and eligibility differ.
No agent wallet bootstrap. Callers still need a funded agent wallet. See how to set up an AI agent wallet.
Related playbooks
Human Checkout Crypto on Stripe: how to accept stablecoin payments on Stripe.
Protocol x402 without Stripe: how to accept x402 USDC payments from AI agents.
Facilitator selection: how to choose an x402 facilitator for USDC.
Circle Gateway nanopayments: how to make a Circle Agent Nanopayment in USDC.
Agent wallet bootstrap: how to set up an AI agent wallet.
FAQ
How do I accept x402 USDC payments on Stripe?
Enable Stablecoins and Crypto, create a Base deposit address with Stripe-Version 2026-05-27.preview, wire x402 middleware with CDP facilitator keys, and record settles as PaymentIntents with transaction_verification.
What is the difference between Stripe Machine x402 and Checkout Crypto?
Machine x402 is agent HTTP micropayments (docs example $0.01 on Base) recorded as PaymentIntents. Checkout Crypto is human wallet checkout at 1.5% with a $10k per-transaction cap.
When should I email machine-payments@stripe.com?
Email that address with your Stripe account ID when you operate outside the US and need stablecoin machine payments in 30+ countries, or when you want Directory listing after integration.
Why is New York excluded from stablecoin machine payments?
Stripe documents stablecoin machine payments as available in all US states except New York. If your entity is NY-based, you need another accept path or Stripe confirmation before go-live.
What USDC networks does transaction_verification support?
As of September 2026 Stripe docs: Tempo, Base, and Solana, with the contract addresses listed in the table above. The x402 sample path uses Base.
Should I use Stripe Machine x402 or Circle Agent Nanopayments?
Use Stripe Machine x402 when you want Stripe balance, PaymentIntents, and Dashboard reporting. Use Circle Agent Nanopayments when you want Gateway USDC balance and Circle CLI x402 pays.
Do I need Coinbase Developer Platform keys for Stripe x402?
Yes for the mainnet path in Stripe's x402 guide: settlement runs through the CDP facilitator, so you need CDP API key id and secret in createFacilitatorConfig.
Next step
Request Stablecoins and Crypto in Dashboard, create one Base deposit address on API version 2026-05-27.preview, wire the docs $0.01 /paid sample with CDP keys, settle one real micropayment, then confirm the PaymentIntent before you advertise agent pricing.
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.
){kind=link}