Networks and tokens

Choose a network and token from the API before creating an invoice or deposit. The token’s name alone is not enough: the request needs its address on that network.

Read available networks

curl 'https://platform.invoise.me/api/v1/networks'

Use these fields from each network:

Field	Purpose
chain_id	network ID.
family	solana or tron for those networks; absent or evm for EVM networks.
tokens[].address	token address: a contract on EVM and Tron, a mint on Solana.
tokens[].decimals	number of decimal places.
tokens[].status	readiness, when present. Use ready assets for live payments.
minimum_payment	the smallest invoice amount on this network, in whole tokens.

The public catalogue describes configured networks. A merchant may have a smaller enabled set; check GET /api/v1/merchants/{merchant_id}/networks with a session during setup. The API rejects invoice or deposit creation on an unavailable network or asset.

Solana and Tron need a recipient set on the shop before the first invoice. See Solana and Tron.

Networks and tokens change through platform settings. Read availability, addresses and decimals from the API when selecting an asset; do not maintain a fixed list.

Minimum payment

minimum_payment is a whole number of tokens, for example "1". An invoice below it returns 400 amount_below_minimum. Both network lists return it. The value differs between networks and can change, so read it instead of hardcoding it.

Format the amount

Payment amounts are strings of whole numbers in the token’s smallest units:

Token decimals	10 tokens in the request
6	"10000000"
18	"10000000000000000000"

Do not send "10.5". At 6 decimals, 10.5 tokens is "10500000". Use integer arithmetic (BigInt in JavaScript) for API amounts; floating-point numbers can lose precision.

One exception: an invoice that offers several tokens or networks takes a decimal token amount, such as "10.5". See several tokens or networks.

Read fees and payout thresholds

curl 'https://platform.invoise.me/api/v1/shops/{shop_id}/terms' \
  -H 'Authorization: Bearer ivk_...'

The response lists terms per network:

Field	Purpose
invoice and deposit	fee settings: bps, minimum, maximum.
sweep_threshold	how much a deposit needs before a payout is scheduled.
minimum_sweep and maximum_sweep	the advertised range for that setting.

bps means hundredths of a percent: 50 bps = 0.5%. Fee minimum and maximum use eighteen-decimal units, independently of token decimals; 10000000000000000 means a 0.01-token fee. sweep_threshold is a human-readable token amount, such as "1".

The maximum fee is not the maximum payment amount. Keep fees, invoice amounts and deposit thresholds separate.