Skip to main content
GET
/
v1
/
fees
/
crypto-payout
cURL
curl --request GET \
  --url https://api.nxos.io/v1/fees/crypto-payout \
  --header 'Authorization: <authorization>'
{
  "fixed": "50.00",
  "bps": 0,
  "asset": "USD"
}

Headers

Authorization
string
required

Bearer token. Format: Bearer <api_key>

Query Parameters

chainName
enum<string>
required

Chain to price the payout on. Must exactly match the chainName you'll send on the payout submit — quoting one chain and paying on another returns the wrong schedule. See ChainName for the full list of accepted values (mainnets + sandbox testnets). Blockchain network identifier.

Production (use these on the live API): ETHEREUM_MAINNET, ARBITRUM_ONE, BASE_MAINNET, BSC_MAINNET, SOLANA_MAINNET, TRON_MAINNET.

Sandbox (testnets — use these only in the sandbox environment): ETHEREUM_SEPOLIA, ARBITRUM_SEPOLIA, BASE_SEPOLIA, BSC_TESTNET, SOLANA_DEVNET, TRON_NILE.

The chain you quote here must exactly match the chainName you send when submitting the payout (POST /v1/transactions/crypto-payouts) — a mismatch is the most common cause of an unexpected fee or a 404/invalid_request.

Available options:
ETHEREUM_MAINNET,
ARBITRUM_ONE,
BASE_MAINNET,
BSC_MAINNET,
SOLANA_MAINNET,
TRON_MAINNET,
ETHEREUM_SEPOLIA,
ARBITRUM_SEPOLIA,
BASE_SEPOLIA,
BSC_TESTNET,
SOLANA_DEVNET,
TRON_NILE
asset
string
required

Asset code being sent (e.g. USDC, USDT).

Response

The request has succeeded.

Fee schedule for a given transaction type + asset (+ method or chain). Describes the pricing rule without running a calculation — clients apply it to their own amount to display a running total:

fee = fixed + round(amount × bps / 10_000)

where bps are integer basis points (1 bp = 0.01%) and rounding is half-up at the asset's subunit precision. Clients displaying the fee before the user commits can calculate locally; the server re-validates at submit time (via the payout request's expectedFeeSchedule), so a stale local rate can't result in a wrong charge — it just fails the submit with a drift error, prompting the client to refresh.

Missing fees (a currency or chain not explicitly priced) return zeros across the board — adding a new asset without a configured fee rule means it's free.

fixed
string
required

Flat component charged regardless of the principal. Zero when the schedule has no fixed component.

bps
integer<int32>
required

Rate applied to the principal, in basis points (1 bp = 0.01%, so 50 bps = 0.5%). Zero when the schedule has no rate component.

asset
string
required

Asset code the schedule is denominated in. Fees are always charged in the same asset as the principal — no FX.