The x402 facilitator for USD and EUR agent payments

Accept x402 agent payments in USD or EUR without running chain infrastructure, holding funds, or giving up settlement control. Non-custodial, live on Base mainnet, no facilitator fee, no signup.

non-custodial Base mainnet · eip155:8453 USDC + EURC no facilitator fee open · no auth · no account

Non-custodial by construction

The facilitator does exactly two things: it verifies signed payment authorizations (the buyer's EIP-3009 signature, the EIP-712 domain, and that the payment matches your declared requirements) and it submits the settlement transaction on-chain. The transfer moves funds directly from the buyer's wallet to yours in a single transaction.

• ArisPay does not hold customer funds, maintain merchant balances, or operate escrow.
• There are no payouts to release — settlement is the payout.
• It verifies payments, not fulfillment: confirming a payment's requirements are met and returning the verification/settlement result to your server. Delivering what you sold remains your server's job.

Point your server at it

Any x402 server can use it as its facilitator. With the paygate SDK it's already the default:

// paygate (Express / Fastify) — facilitator.arispay.app is the default
const pw = paygate({ merchantId: "m_123" });
app.get("/api/thing", pw({ priceCents: 10 }), handler);   // $0.10 in USDC

// price in euros instead — settles EURC on Base
const pwEur = paygate({ merchantId: "m_123", currency: "EUR" });
app.get("/api/eu-thing", pwEur({ priceCents: 50 }), handler); // €0.50 in EURC

// any other x402 middleware — set the facilitator URL
{ facilitatorUrl: "https://facilitator.arispay.app" }

What it costs

ArisPay charges no facilitator fee. Verification is free; settlement gas (~$0.001 on Base) is the chain's cost, paid by the seller — either directly (self-submitted with your own key as SDK self-settle support rolls out) or reimbursed at exact cost, zero margin, at netted payout. During launch, ArisPay's relayer fronts limited gas for relayer-submitted direct settles within a bounded daily budget; any change to that allowance comes with at least 30 days' notice. The live policy is machine-readable in the fees block of /supported.

EUR-native

Settles EURC alongside USDC on Base — price your API in euros without running your own infrastructure. The validated asset registry (with on-chain-verified EIP-712 domains) is served live at /facilitator and /trust.

Merchant observability, no account required

Every verify/settle response carries a requestId; settlement is idempotent on the EIP-3009 nonce (duplicates are rejected, never double-settled). Look anything up after the fact:

• GET /receipts/{txHash} — settlement receipt by transaction hash
• GET /settlements/{nonce} — settlement status by payment id (the EIP-3009 nonce)
• GET /status — service status; GET /metrics — uptime, latency, settlement counts + success rate
• GET /events/schema — webhook event model (payment.verified, payment.settled, payment.failed, settlement.confirmed, settlement.failed — schema published now, delivery upcoming)

Why ArisPay instead of another facilitator — or self-hosting?

• Non-custodial: funds move buyer → seller directly; there is no balance to trust us with.
• No account, no API key: point facilitatorUrl here and you're live.
• USD and EUR: USDC + EURC on Base mainnet, with on-chain-verified EIP-712 domains.
• Transparent fee and gas policy: no facilitator fee; the machine-readable policy in /supported is the contract.
• Observability built in: receipts, settlement status, request ids, metrics — without signing up.
• Simple integration: default in paygate (accept) and paired with payagent (pay).
• Vs self-hosting: no relayer key management, RPC infrastructure, replay protection, or monitoring to run — and you keep settlement control, since nothing custodial sits between you and the chain.

Verify every claim on this page

The endpoints

• POST /verify — verify a signed payment payload (free; returns requestId)
• POST /settle — verify and settle an EIP-3009 payment on-chain (idempotent on the nonce)
• GET /supported — supported kinds + the live production block + fee policy
• GET /facilitator — discovery document
• GET /receipts/{txHash}, GET /settlements/{nonce} — receipt + status lookup
• GET /trust, GET /status, GET /metrics, GET /events/schema

Open, no auth, matching the x402 facilitator protocol (also mirrored under /facilitator/*).

FAQ