Robinhood Chain x402 lane

developer

How x402 payments reach Robinhood Chain through the Meridian facilitator, while Bankr x402 Cloud stays Base-settled where configured.

HISS vault services can be paid for over x402 on two documented lanes. Bankr x402 Cloud is the existing production paid-service rail and currently settles on Base where configured. Meridian documents x402 facilitator support for Robinhood Chain with USDG — HISS uses Meridian as the Robinhood Chain x402 lane when configured and verified.

The two lanes

Meridian facilitator — Robinhood Chain (4663), USDG. Documented at supported-networks (verified 2026-07-08). Mainnet-only; enabled by server-side env (MERIDIAN_ENABLED, MERIDIAN_API_KEY); status at /api/x402/meridian/status. Details: Meridian x402.
Bankr x402 Cloud — Base, USDC. Eleven HISS endpoints live today; the vault services are deployable scaffolds on this lane. Status at /api/x402/bankr/status.
Self-hosted facilitator — disabled research candidate. Superseded in practice by Meridian; the notes remain at the historical candidate page.

Lane selection

For vault services, HISS prefers the Meridian lane when it is enabled and configured, and otherwise uses the Bankr lane — always labeled, never a silent downgrade. Every schema and receipt carries the provider, the payment chain, and the reason for the selection. Whatever lane a payment takes, vault deposits and vault contracts remain on Robinhood Chain.

Hard rules

Meridian keys are server-only; no key or secret ever appears in a response or a client bundle.
The server rebuilds payment requirements on every request and fails closed on any buyer-supplied price, asset, network, or recipient mismatch.
Payment receipts are deterministic and persisted to Postgres with liveOrderSent: false.
The vault chain is never described as Base, and x402 is never described as native to Robinhood.

$HISS is independent research software in pre-execution readiness checks — not investment advice, and not affiliated with Robinhood, Bankr, or Chainlink.