Coverage

Stablecoins and chains

Each asset is deliverable only on chains its issuer natively supports. There are no wrapped or bridged variants. Solana is live at launch. The EVM chains are built and enable next, and the euro assets return with the EUR rail.

A chain that is not yet enabled returns 400 unsupported_chain on wallet creation, and its corridors do not appear in GET /api/corridors.

Fiat rails

Rails differ in limits and settlement speed, which is why currency and rail are both explicit on every virtual-account create. There is no default to guess.

Deposit instructions always use the rail's native vocabulary, inside the same deposit_instructions object, so a new rail arrives without reshaping your integration. A USD account also exposes routing_number_ach, routing_number_wire, and routing_number_rtp where the bank differentiates them.

Discover, do not hard-code

The tables above describe the platform. Your account's live pairs, with your effective fees and limits, are served by the API:

curl -s $BASE/api/corridors -H "Api-Key: $KEY"

{
  "data": [
    {
      "object": "corridor",
      "service": "onramp",
      "source": {"asset": "usd", "rail": "ach"},
      "target": {"asset": "usdc", "chain": "solana"},
      "min_amount": "1",
      "max_amount": "1000000",
      "fees": {
        "bps": "30",
        "spread_bps": "0",
        "min": "0.30",
        "collection": "monthly"
      },
      "estimated_settlement": "instant"
    }
  ]
}

Build corridor pickers and validation from this endpoint rather than from these tables. Corridors are account-scoped configuration, and a new one appears here the moment it is enabled for you.

service is one of onramp (fiat in, stablecoin delivered), offramp (stablecoin in, the bank account paid directly), or swap (stablecoin to stablecoin). Only onramp is live at launch.