Three days ago, Stripe and Paradigm launched Tempo (a payments-focused L1 blockchain) alongside MPP (Machine Payments Protocol). Simultaneously, Coinbase's x402 crossed 75M transactions. Google launched UCP. This is the agent payments Big Bang.
Core Question: How should yonatan-hq's M39 commerce milestone adapt to a world where AI agents are autonomous economic actors?
@stripe/acp-mcp-server| Aspect | Detail |
|---|---|
| Launch | March 18, 2026 (3 days ago) |
| Status | Private Preview — requires API version 2026-03-04.preview |
| Flow | Agent requests resource -> HTTP 402 -> Agent pays -> Resource delivered |
| Networks | Tempo (USDC), Stripe card networks (all Stripe currencies) |
| Auth | Sessions model — authenticate once, spend within budget limit, batch settle |
| Credentials | SharedPaymentTokens (SPTs) — single-use, time-limited, scoped to one tx |
| Settlement | Into existing Stripe balance, standard payout schedule |
| Min payment | $0.01 USDC |
| Tooling | Stripe Agent Toolkit (Python/TS), MCP server at mcp.stripe.com |
| Geo restriction | US businesses only for stablecoin acceptance. Cards: 46 countries (Israel NOT listed) |
| Partners | Visa, Anthropic, OpenAI, Mastercard, Shopify, Lightspark (Bitcoin/Lightning) |
| Key advantage | Fiat + crypto hybrid, sessions for throughput, existing Stripe ecosystem |
| Aspect | Detail |
|---|---|
| Launch | Mid-2025 (Coinbase + Cloudflare) |
| Status | Live — 75M+ transactions, $24M volume |
| Flow | HTTP request -> 402 + PAYMENT-REQUIRED header -> Client pays -> Retry with PAYMENT-SIGNATURE |
| Networks | Base (EVM), Solana — token-agnostic across EVM chains |
| Auth | Per-request (pay, get resource, repeat). "upto" scheme planned but not shipped |
| Settlement | On-chain (<2 sec on Solana) |
| Fees | Zero protocol fees — only nominal network fees |
| Min payment | No minimum. $0.001 viable. |
| Tooling | @x402/fetch, @x402/express, Python/Go clients |
| Geo restriction | None — permissionless, no accounts needed |
| Partners | Coinbase, Cloudflare, Vercel, AWS, Nansen, Alchemy |
| Key advantage | Zero fees, truly open, 1-line server middleware, no accounts |
| Key weakness | Crypto only — no fiat rails. Avg tx $0.20 (mostly testing/gamified) |
| Aspect | Detail |
|---|---|
| Launch | December 2025 (Stripe Sessions), spec v2026-01-30 |
| Status | Beta — open-source spec on GitHub |
| Purpose | Full commerce protocol (not just payments) — discovery, checkout, fulfillment |
| Flow | Agent discovers merchant -> Creates checkout -> Shares SPT -> Completes -> Gets order events |
| Spec | 4 REST endpoints: create_checkout, update_checkout, complete_checkout + events |
| MCP | @stripe/acp-mcp-server — exposes ACP as MCP tools for any LLM agent |
| Catalog | Merchants sync product catalog to Stripe -> agents discover via ACP |
| Payments | Uses SPTs (SharedPaymentTokens) — wraps any Stripe payment method |
| Merchants | URBN (Anthropologie, Free People, Urban Outfitters), Etsy, Coach, Kate Spade |
| Platforms | Wix, WooCommerce, BigCommerce, Squarespace, commercetools integrated |
| AI Agents | ChatGPT "Instant Checkout" powered by ACP |
| Key advantage | Full commerce lifecycle, not just payment — discovery through fulfillment |
| Dimension | MPP | x402 | ACP |
|---|---|---|---|
| Scope | Payments only | Payments only | Full commerce lifecycle |
| Fiat support | Yes Cards/BNPL | No | Yes via SPTs |
| Crypto support | Yes USDC/Tempo | Yes USDC/Base/Sol | Yes via MPP/x402 |
| Israel support | No (US only for stablecoin) | Permissionless | Depends on Stripe IL |
| ILS currency | No | No (USDC only) | If Stripe supports IL |
| Micropayments | $0.01+ | $0.001+ | Standard pricing |
| Setup complexity | Medium (Stripe account) | Low (1 line) | High (catalog sync) |
| MCP integration | Via Stripe MCP | Custom | Native |
| Maturity | 3 days old | ~9 months | ~3 months |
Critical: Israel is NOT in Stripe's 46 supported countries for direct merchant accounts. Stripe has a "payments in Israel" guide but positions itself for international businesses selling TO Israel, not Israeli businesses.
Implication: MPP and ACP are not directly usable by an Israeli Osek Morsheh. PayPlus/Grow remain mandatory for ILS transactions. Stripe MPP is relevant only for USD international sales or as an outbound payment method (your agents paying foreign services).
docs.payplus.co.ilpayment_provider: "grow"| GreenInvoice | iCount | |
|---|---|---|
| API | REST API | REST API |
| SHAAM | Integrated | Integrated |
| Webhooks | Yes | Limited |
| Developer DX | Better docs | Older API |
| Recommendation | GreenInvoice — better API, SHAAM-ready | |
Use case: Customer orders via WhatsApp/Portal
Payment: PayPlus/Grow (ILS)
Status: M39 #613 + #614 + #1102. Must build. Legally required for IL.
Use case: Your agent pays Prodigi, APIs, MCP tools
Payment: Stripe MPP / x402 (USD)
Status: Future opportunity. MPP is 3 days old, private preview, US-only for stablecoin. Build the protocol interface now, wire MPP later.
Use case: AI agents discover & buy your products
Payment: ACP + SPTs
Status: Strategic future. Requires Stripe account (IL issue) + catalog sync. URBN/Etsy already live. Could be transformative if Stripe opens IL.
| Category | Tool | Description |
|---|---|---|
| Account | get_stripe_account_info | Retrieve account details |
| Balance | retrieve_balance | Current + pending balance |
| Customer | create_customer, list_customers | Manage customers |
| Product | create_product, list_products | Product catalog |
| Price | create_price, list_prices | Pricing management |
| Payment | create_payment_link, create_payment_intent | Accept payments |
| Invoice | create_invoice, list_invoices | Invoice management |
| Subscription | list_subscriptions, cancel_subscription | Recurring billing |
| Refund | create_refund | Process refunds |
| Dispute | list_disputes | Handle chargebacks |
| Search | search_stripe_documentation | Knowledge base search |
Remote MCP: mcp.stripe.com (OAuth2 via Stripe Connect) | Local: npx @stripe/mcp --tools=all
Click to select your preferred approach:
Recommended
Build PayPlus/Grow + GreenInvoice now (legal requirement). Design PaymentProvider protocol with MPP adapter slot. Wire Stripe MCP as hq-platform tool. Add MPP when Israel is supported.
Blocked
Wait for Stripe Israel support, build entirely on Stripe + MPP + ACP. Skip Israeli gateways.
Over-engineered
Build both Israeli gateways AND Stripe MPP simultaneously. Full ACP catalog sync. Full x402 support.
Scoring criteria: Legal requirement (3x weight) + Revenue impact + Technical feasibility + Solo-dev effort + Time-to-value
PaymentProvider + InvoiceProvider protocols (Protocol DI)GrowProvider (already have integration) + PayPlusProviderGreenInvoiceProvider with SHAAM allocation.mcp.json (free, immediate value for dashboard ops)assistant_mode="commerce" for AllowedChatsStripeProvider for USD international payments (if Stripe opens IL, or via US entity)StripeMPPProvider stub with feature flagBuild Israeli rails NOW, design for agent economy TOMORROW.
PayPlus + GreenInvoice are legally required and revenue-generating today. MPP/ACP/x402 are 3 days old, US-only, and have ~$28K daily volume. The PaymentProvider protocol abstraction costs zero extra effort and makes you MPP-ready the day Stripe opens Israel.
Meanwhile: add Stripe MCP to your hq-platform tools TODAY (free, instant value for ops).