What is x402 EUR settlement? A definitive guide for AI agent payments

What is x402?

x402 is an open payment protocol that revives the long-dormant HTTP 402 "Payment Required" status code for the era of autonomous AI agents. Originally proposed by Coinbase in 2025, x402 lets any HTTP API request payment from a client agent in stablecoins, on-chain, in a single round-trip. The agent receives a 402 response containing payment requirements; it submits a signed payment proof in a follow-up header; the resource server forwards the proof to a facilitator for verification and settlement, then returns the actual response.

The protocol's core innovation is that it removes credit-card-era assumptions — no merchant accounts, no card-network fees, no chargebacks, no human-in-the-loop. An AI agent can discover, pay and consume an API in a few hundred milliseconds.

Today x402 is supported by Coinbase CDP, Tempo, Stripe (via the parallel MPP / Machine Payments Protocol), and an ecosystem of facilitators including AsterPay in the EU.

What does "EUR settlement" mean?

In payments, settlement is the moment money lands in the merchant's account in spendable form. For an x402 payment that means the difference between two outcomes:

• USDC settlement (default Coinbase CDP) — the merchant receives USDC on Base. They still need to convert it to EUR somewhere else (an exchange, a CASP, an OTC desk) before they can pay rent or salaries.
• EUR settlement (AsterPay) — the merchant receives EUR on their bank account, with a SEPA reference, ready for accounting and VAT. The conversion happens inside the same x402 flow, automatically.

For European merchants this is the difference between "I now have to do crypto bookkeeping" and "I don't even need to know my customer was an agent." The x402 EUR-settlement layer is the operational seam between agent-native commerce and Continental European banking.

Why do AI agent payments need EUR settlement?

European merchants invoice in euros, file VAT in euros, and pay salaries in euros. An on-chain stablecoin payment is great for the agent but creates three problems for the merchant:

1. Accounting friction — every USDC inflow needs an EUR-equivalent valuation at the time of receipt, plus a separate journal entry when it is later converted. Multiply by hundreds of agent-driven micropayments per day and the bookkeeping is unviable.
2. VAT timing risk — under EU VAT rules, the taxable event is the moment of supply in EUR. If the merchant converts USDC days later at a different rate, the VAT base shifts and reconciliations get messy.
3. Treasury exposure — even EUR-denominated stablecoins like EURC carry counterparty risk that most SMEs are not equipped to evaluate.

EUR settlement collapses all three problems into a single flow: the agent pays USDC; the merchant sees EUR on their bank statement; the SEPA reference includes the original x402 payment ID for one-click reconciliation.

How does USDC → SEPA Instant work in practice?

Here is the actual flow inside an AsterPay-facilitated x402 payment, end to end:

1. Agent calls   GET https://merchant.example.com/api/data
2. Merchant API  → returns HTTP 402 + WWW-Authenticate: Payment header
                   (facilitator: x402.asterpay.io, asset: USDC on Base, 0.05 USDC)
3. Agent signs a USDC permit + sends payment header
4. Merchant API  → forwards proof to AsterPay /v2/x402/settle
5. AsterPay      a) verifies signature on Base
                 b) auto-routes USDC → EUR via best CASP partner of 4
                 c) pushes EUR via SEPA Instant to merchant IBAN
                 d) returns 200 OK + Payment-Receipt header
6. Merchant API  → returns the actual API response to the agent
7. Total elapsed time: ~7 seconds (P50), ~10 seconds (P95)

The merchant never holds USDC. The agent never holds EUR. AsterPay is non-custodial — funds pass through licensed CASP partners under MiCA, never sitting on AsterPay's balance sheet. The whole flow is a single HTTP retry from the agent's perspective.

Who runs x402 EUR facilitators today?

As of April 2026 the landscape is small but consolidating. Here is a snapshot:

Source: AsterPay competitive landscape audit, April 2026. See /compare for the full side-by-side methodology.

Is x402 EUR settlement regulated under MiCA?

Yes. EUR settlement of stablecoin payments falls within the scope of the EU's Markets in Crypto-Assets Regulation (MiCA), which entered full application in December 2024. Two activities are clearly captured:

• Exchange of crypto-assets for funds — the USDC-to-EUR swap is a regulated CASP service.
• Custody and administration of crypto-assets — applies if the facilitator holds the agent's stablecoin even momentarily.

AsterPay's architecture is intentionally non-custodial: the swap is executed atomically through licensed CASP partners; AsterPay never takes title to the USDC. This places the regulatory burden on the partners (who are already authorised) and lets AsterPay operate as a payment-orchestration layer while AELIRA LTD pursues direct CASP authorisation. The full regulatory map for AsterPay's 2026 roadmap is documented at /mica-compliance.

How much does x402 EUR settlement cost?

AsterPay's published pricing for the EUR-settlement layer is:

• 0.50% (50 bps) on the EUR settlement amount, billed to the merchant.
• + underlying CASP partner spread, typically 30-80 bps depending on volume and currency pair. Surfaced transparently in the /v1/settlement/estimate response.
• No monthly fees, no per-transaction KYC fees, no SEPA Instant surcharge, no setup fees.

For comparison, Stripe's standard European card pricing is 1.4% + €0.25 for European cards and 2.5% + €0.25 for non-European cards, plus an FX markup of roughly 2% if the customer pays in a currency other than EUR — and settlement still takes 2-7 days. PayPal sits at 2.49% + fixed fee. Raw x402 via Coinbase CDP is essentially free at the protocol layer but leaves the EUR conversion as the merchant's problem.

How long does USDC to EUR via SEPA Instant take?

End-to-end latency in production is under 10 seconds (P95). The breakdown:

• USDC settlement on Base: 2-4 seconds (block finality).
• CASP swap USDC → EUR: 1-3 seconds.
• SEPA Instant push to merchant IBAN: 1-3 seconds.

SEPA Instant operates 24/7/365 across all 36 EU/EEA countries, including weekends, evenings and bank holidays. Since the European Commission's Instant Payments Regulation entered force in January 2025, every euro-area bank is required to offer SEPA Instant with the same fee as a regular SEPA credit transfer — which removed the last commercial obstacle to instant euro payouts.

What chains and stablecoins does AsterPay accept?

AsterPay's x402 facilitator accepts payments on five EVM chains with native USDC and on Bitcoin Lightning:

How do I integrate x402 EUR settlement?

Three integration paths, in order of complexity:

1. MCP server — npm install @asterpay/mcp-server. Works with any LLM agent that speaks Model Context Protocol (Claude, GPT-5, Gemini agents). 16 tools out of the box.
2. Python SDK — pip install asterpay. Three lines: instantiate, call endpoint, get EUR receipt.
3. Direct HTTP API — https://x402.asterpay.io. Full Swagger/OpenAPI at /docs. Free endpoints (KYA trust score, settlement estimate) require no auth.

A merchant onboarding takes about 10 minutes through Sumsub KYB; after that, payouts run automatically with no per-transaction KYC and no manual off-ramp.

Related reading

• What is x402? — protocol explainer
• What is an x402 facilitator?
• What is KYA (Know Your Agent)?
• ERC-8004 explained — on-chain agent identity
• EUR settlement for AI agents — buyer's guide
• How AsterPay compares — Stripe, Wise, BVNK, raw x402
• MiCA compliance — AsterPay's regulatory roadmap

Have a correction or want this page to cover a different angle? Email [email protected]. We update this page every quarter.