Skip to content

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.

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

For prices only, GET /api/v1/pricing returns the fees a new merchant starts with on each network, the referral discount and the card prices, in dollars. It needs no credentials, any website may call it, and it is cached for five minutes.

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 during setup, with a session or a shop API key with read (the key’s merchant ID is in GET /api/v1/me). 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 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.

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.

These are the general fees a new merchant starts with; fees can differ from one merchant to another, so read yours from the API (below). The fee is 0.5% of each invoice or of each deposit payout, never less than the network’s minimum fee and never more than $10. The minimum covers the gas of your payout.

Network Fee Minimum fee Maximum fee Minimum payment
Ethereum 0.5% $1 $10 $10
Arbitrum 0.5% $0.05 $10 $1
Base 0.5% $0.03 $10 $1
Optimism 0.5% $0.03 $10 $1
Polygon 0.5% $0.05 $10 $1
BNB Chain 0.5% $0.05 $10 $1
Avalanche 0.5% $0.02 $10 $1
Solana 0.5% $1 $10 $2
Tron 0.5% $4.50 $10 $10

For example, $100 on Base costs $0.50, $4 costs the $0.03 minimum, and $5,000 costs $10 instead of $25.

A merchant that signed up through a referral link starts at 0.49%. A merchant keeps the fees it was created with, and Invoise can set individual fees, so read your shop’s own terms from the API as shown below.

Terminal window
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". To change it, send PATCH /api/v1/shops/{shop_id} with {"sweep_thresholds":{"<chain_id>":"25"}}, within that network’s minimum_sweep and maximum_sweep; a value outside returns 400 invalid_sweep_threshold.

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