Networks and Currencies Information
This section describes how to retrieve reference data for supported blockchain networks and available currencies.
These endpoints are used to build payment forms, validate user input, and ensure that payment orders are created using supported parameters.
Important:
All endpoints described in this section are public and do not require authentication or signature headers.
Get Available Networks
Returns the list of blockchain networks supported by the crypto acquiring system.
Endpoint
- HTTP Method:
GET - Endpoint:
/api/public/v1/acquiring/networks - Authentication: Not required
Example Response
{
"success": true,
"data": {
"networks": [
"ethereum",
"bsc",
"tron",
"bitcoin"
]
}
}Response Description
| Field | Type | Description |
|---|---|---|
networks | Array of strings | List of supported blockchain network identifiers |
The returned network identifiers must be used as the network parameter when creating a payment order.
Get Currencies by Network
Returns the list of available currencies (native coins and tokens) for a specific blockchain network.
Endpoint
- HTTP Method: GET
- Endpoint:
/api/public/v1/acquiring/{network}/currencies - Authentication: Not required
Path Parameters
| Parameter | Type | Description |
|---|---|---|
network | String | Blockchain network identifier (from the networks list) |
Example Response
{
"success": true,
"data": [
{
"token_address": "bc1000000000000000000000000000000000000000",
"name": "Bitcoin",
"symbol": "BTC",
"decimals": 8
}
]
}Response Description
Each object in the response represents a supported currency for the selected network.
| Field | Type | Description |
|---|---|---|
token_address | String | Token contract address or internal identifier for native coins |
name | String | Full currency name |
symbol | String | Currency symbol |
decimals | Number | Number of decimal places used by the currency |
The token_address value must be used when creating a payment order to specify the payment currency.
Usage Notes
-
These endpoints can be safely called from frontend applications
-
The data can be cached to reduce API calls
-
Networks and currencies may be extended over time, always rely on these endpoints instead of hardcoding values
This reference data is typically used before payment creation to allow the customer or merchant system to select a valid network and currency.