Facilitator

The ax402 facilitator verifies signed payment authorizations and submits on-chain settlement transactions on behalf of gateway servers. Gateway processes call the facilitator over HTTP; buyers never talk to it directly.

Role in the stack

• Gateway receives PAYMENT-SIGNATURE from the buyer
• Gateway calls facilitator /verify then /settle
• On success, gateway proxies the request to upstream

Hosted facilitator

Ax402 provisions a dedicated facilitator URL for each seller. Use the base URL shown on the dashboard Facilitator page; do not call the shared upstream facilitator directly.

Requests through your dedicated Live URL are attributed to your account, checked against your billing quota, and metered when /settle succeeds. The dashboard labels the active URL as Mainnet (Live) or Sandbox / testnet (Sandbox).

Supported networks, schemes, and chain IDs come from GET /supported — match endpoint accepts to those capabilities before you publish routes. Each capability row includes the CAIP-2 network, numeric chain ID where applicable, and an explorer link when available.

# Copy your base URL from Dashboard → Facilitator
FACILITATOR_BASE_URL="https://your-facilitator.example"
curl -s "$FACILITATOR_BASE_URL/supported" | jq .

In Sandbox mode, switch the dashboard to Sandbox and use the base URL shown there.

Enterprise self-hosted

AxLabs can deploy a dedicated facilitator in your environment for enterprise customers — private key custody, custom networks, and SLA-backed operations. This is not self-service; contact us to discuss requirements.

Related

• Gateway & dashboard
• Control plane API
• x402 protocol spec