> For the complete documentation index, see [llms.txt](https://docs.pay.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pay.io/assets/asset-management-add-edit-disable/asset-networks.md).

# Asset Networks

In the Pay.io ecosystem, an Asset Network refers to the specific blockchain infrastructure used to process a cryptocurrency transaction. While an "Asset" is the currency itself (like USDT or Ethereum), the "Network" is the road that currency travels on.

{% hint style="success" %}
See the list of supported assets and networks in [List of Available Assets](/assets/asset-management-add-edit-disable/list-of-available-assets.md). 
{% endhint %}

#### Single-Network vs. Multi-Network Assets

* Native Assets are cryptocurrencies that exist on their own dedicated blockchain. For example, Bitcoin (BTC) is always traded on the Bitcoin Mainnet, and Solana (SOL) is traded on the Solana Mainnet.
* Multi-Network Assets are stablecoins like USDT and USDC. They are unique because they can exist on multiple different blockchains. For example, a user can choose to send USDT using the Ethereum network (ERC-20), the Tron network (TRC-20), or the Polygon network. The value of the coin is the same, but the speed and cost of the transaction depend on the network chosen.

### Why Does Network Selection Matter?

When configuring assets in the Merchant Console or depositing via the Cashier UI, selecting the correct network is critical for two reasons:

* Fees and speed\
  Different networks have different congestion levels. We support multiple networks (such as Polygon, Arbitrum, and Base) to offer users flexibility on transaction costs (gas fees) and processing speeds.
* Compatibility\
  A deposit must be sent to a wallet address that matches the specific network. Sending funds to the wrong network type can result in lost assets.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pay.io/assets/asset-management-add-edit-disable/asset-networks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.