Supported Networks

recv is non-custodial: every invoice settles directly to your own wallet on the network you choose. You connect payout wallets per network in the Merchant Console, and the payable_network you pass when creating an invoice determines which wallet receives the funds.

Payable networks

These are the values accepted for payable_network:

Values are case-insensitive in the request and normalized to uppercase. To choose a non-default asset, pass payable_asset or a payment_options entry, for example { "network": "TON", "asset": "USDT" }. The legacy TON_USDT value is still accepted as an alias for TON + USDT, but new integrations should not use it.

Wallet buckets

BASE, ARBITRUM, and BSC share a single EVM wallet bucket — one connected 0x… address can serve as the destination for those EVM networks. TON assets share a TON wallet bucket. TRON and SOLANA use their own buckets.

Wallet networks

When connecting a payout wallet, the network is one of TON, TRON, SOLANA, or EVM. Address validation per network:

Amounts and precision

base_amount_usd is a USD decimal string. Stablecoins are priced 1:1 with USD. Native GRAM on TON, SOL, and BNB are converted at invoice creation, and invoices containing a native volatile asset use a shorter payment window.

Payment comments / memos

An invoice may include multiple payment_options. For native GRAM on TON the option includes a required memo in payment_comment; for stablecoins and other native options matching uses the exact amount, network, asset, and destination address. Surface the exact option amount prominently in your checkout.

recv only supports the networks listed above. Do not assume any other chain is available.