Skip to main content
GET
See which currencies you can charge in — BTC, ETH, USDT, DOGE and more. Populate your checkout’s currency picker from this endpoint instead of hardcoding tickers: only currencies in this list are accepted by POST /api/v1/payments.
The response shape depends on whether the credential carries a merchant context. With one, you get an array of objects; without one you get a bare array of ticker strings. Type the branch you expect — a client that assumes objects will read undefined for every field when an admin token is used.

​
Authorization

Any valid credential (secret API key or dashboard JWT). See the Authentication guide. This endpoint takes no parameters — the credential alone decides which of the two response branches you get.

​
The two response branches

With a merchant context (a merchant JWT, or a merchant-scoped lid_live_* key) the route returns the currencies you have an active wallet for, as an array of objects — see the response example above. A fresh merchant account gets a wallet for every platform currency automatically. Without a merchant context — a super_admin dashboard token (admin JWTs carry no merchantId) or a SYSTEM-scoped key — the route returns every ticker in the platform registry as a bare array of strings, with no name and no hasWallet:
200 OK (no merchant context)
Both branches return a top-level array (no {ok, data} envelope); only the element type differs.

​
Response fields

​
string
Currency ticker (e.g. BTC, USDT_ERC20). In the no-merchant-context branch, each array element is this bare string instead of an object.
​
string
Human-readable currency name. Present only in the merchant-context branch.
​
boolean
Whether you have an active wallet for this currency. Present only in the merchant-context branch (which only lists currencies you have an active wallet for).

​
See also