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

# Supported Networks and Assets

Paymento supports native cryptocurrencies, stablecoins, and tokens across multiple blockchain networks.

Supported assets may change as new networks are added, existing integrations are expanded, or an asset is temporarily disabled. Use Paymento’s API or merchant panel as the current source of truth rather than maintaining a hardcoded asset list.

### Get the current asset list

Developers can retrieve supported assets using the following endpoints:

| Endpoint                | Description                                             |
| ----------------------- | ------------------------------------------------------- |
| `GET /v1/coins`         | Returns assets currently enabled on Paymento            |
| `GET /v1/payment/coins` | Returns assets enabled for your store using its API key |

Your customers can only select assets that are both supported by Paymento and enabled for the store. The hosted checkout uses the same store configuration.

See [API Overview](/api-documentation/api-overview.md) and [Get List of Accepted Coins](/api-documentation/additional-apis/get-list-of-accepted-coins.md) for authentication requirements and response fields.

### Supported network types

Paymento currently supports assets across the following blockchain architectures:

| Network type   | Current examples                              |
| -------------- | --------------------------------------------- |
| EVM-compatible | Ethereum and ERC-20 tokens                    |
| Tron           | TRX and TRC-20 tokens                         |
| Solana         | SOL and SPL tokens                            |
| UTXO-based     | Bitcoin, Litecoin, Dogecoin, and Bitcoin Cash |

On account-based networks, the native asset and supported tokens generally use the same underlying wallet account. For example, ETH and supported ERC-20 tokens can be associated with the same Ethereum wallet address.

Support for a network does not necessarily mean that every token on that network is available. Only assets explicitly enabled by Paymento and the merchant’s store can be used at checkout.

### Availability by wallet method

Paymento offers two wallet methods:

* **Bring Your Own Wallet**
* **Paymento Embedded Wallet**

Most supported assets are available with both methods, but some exceptions apply.

| Network or asset                     | Bring Your Own Wallet |         Embedded Wallet |
| ------------------------------------ | --------------------: | ----------------------: |
| Ethereum and supported ERC-20 tokens |             Supported |               Supported |
| Tron and supported TRC-20 tokens     |             Supported |               Supported |
| Solana and supported SPL tokens      |             Supported |               Supported |
| Bitcoin                              |             Supported |               Supported |
| Litecoin                             |             Supported |               Supported |
| Dogecoin                             |             Supported |               Supported |
| Bitcoin Cash                         |             Supported | Not currently supported |

Bitcoin Cash is currently available only through Bring Your Own Wallet. Embedded Wallet support may expand as Paymento adds and validates additional network-specific settlement capabilities.

Always check the merchant panel or supported-assets API before promising a particular asset to customers.

### Customer checkout experience

An asset can be supported under both wallet methods while offering a different customer checkout experience.

| Network type                      | Bring Your Own Wallet     | Embedded Wallet                     |
| --------------------------------- | ------------------------- | ----------------------------------- |
| Supported UTXO-based networks     | Address and QR code       | Address and QR code                 |
| Supported EVM networks and tokens | Connected wallet required | Address and QR code                 |
| Solana and SPL tokens             | Connected wallet required | Address and QR code                 |
| Tron and TRC-20 tokens            | Connected wallet required | Connected wallet currently required |

#### Address and QR-code checkout

The customer receives:

* A receiving address
* The requested crypto amount
* A QR code
* The selected asset and network
* The remaining payment time

The customer can send the payment from a compatible external wallet and, where supported, from an exchange account.

#### Connected-wallet checkout

The customer connects a compatible browser or mobile wallet and approves the transaction from the checkout page.

Depending on the network and device, supported options may include browser extensions, mobile wallets, WalletConnect, or network-specific wallet integrations.

Customers paying from an exchange account or a wallet that cannot connect may be unable to complete a connected-wallet payment.

### Account-based network considerations

With Bring Your Own Wallet, supported account-based networks generally require the customer to connect a compatible wallet. This allows Paymento to reliably associate the transfer with the correct payment request.

Embedded Wallet removes this requirement on supported account-based networks by assigning payment-specific receiving information. This allows customers to pay using a regular address and QR code on supported EVM and Solana assets.

#### Tron and TRC-20

Tron and TRC-20 payments, including USDT-TRC20, currently require a connected wallet under both wallet methods.

Plain address-and-QR checkout is not currently available for Embedded Wallet payments on Tron. This is a limitation of Tron blockchain for settlement implementation in an efficient way, not a merchant-configurable setting.

If accepting stablecoins through a plain address and QR code is important to your business, consider a supported stablecoin on an EVM or Solana network using Embedded Wallet.

### How receiving addresses are assigned

Receiving-address behavior depends on the wallet method and blockchain architecture.

#### Bring Your Own Wallet

* On supported UTXO-based networks, Paymento derives payment addresses from the merchant-provided extended public key.
* On supported account-based networks, payments generally use a connected-wallet flow so Paymento can identify the payer and associate the transaction with the correct order.

Paymento cannot derive private keys or sign transactions using an extended public key or public wallet address.

#### Embedded Wallet

Paymento provides receiving information through the merchant-controlled store wallet. Where supported, each payment can be associated with distinct receiving information so customers can pay without connecting a wallet.

Paymento uses network-specific payment and settlement workflows. The merchant remains the signing authority, regardless of the underlying network.

### USDT across different networks

The same token may be available on multiple networks, but each version is treated as a separate payment asset.

For example:

| Asset      | Network  | Embedded Wallet checkout            |
| ---------- | -------- | ----------------------------------- |
| USDT-ERC20 | Ethereum | Address and QR code                 |
| USDT-SPL   | Solana   | Address and QR code                 |
| USDT-TRC20 | Tron     | Connected wallet currently required |

Customers must send the exact token using the network displayed at checkout. Sending USDT on a different network does not complete the payment, even if the token symbol is the same.

Merchants should clearly show the asset and network together for example, **USDT on Tron (TRC-20)** rather than only **USDT**.

### Testnet support

Paymento provides testnet assets for selected networks so merchants can test their integration without using real funds.

Testnet availability varies by network and wallet method. Testnet assets are identified in the supported-assets response and merchant panel.

Before enabling a store for live payments:

1. Enable the appropriate testnet assets.
2. Create a test payment request.
3. Complete the payment using the correct testnet.
4. Confirm that payment notifications reach your server.
5. Verify the payment through the API.
6. Disable testnet assets before accepting live customer payments unless you still need them.

See [Testing and Simulation](/accept-crypto-payments/testing-and-simulation.md) for instructions.

### Confirmations

Each blockchain and asset can have its own confirmation requirement.

Paymento monitors the transaction and reports its current payment status. Where applicable, the verification response includes:

* Current confirmations
* Required confirmations
* Transaction status
* Transaction hash
* Network information

Do not hardcode confirmation requirements in your integration. Use the current values returned by Paymento and fulfil orders only after the required payment status is reached.

### Amounts and precision

Cryptocurrencies use different decimal precision and display rules. Paymento converts the requested price into the selected cryptocurrency and applies the configured precision for that asset.

Merchants should use the amounts returned by Paymento rather than independently recalculating or rounding the payment amount.

If underpayment tolerance is available for your store, configure it carefully. A tolerance allows an order to be accepted when the amount received is slightly below the requested amount, but it may also allow customers to intentionally pay less.

See [Payment States and Confirmations](/api-documentation/payment-states-and-confirmations.md) for partial payments, overpayments, and tolerance handling.