> ## Documentation Index
> Fetch the complete documentation index at: https://docs.request.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Secure Payment Supported Networks and Currencies

> Chain and currency coverage for Secure Payment Pages.

## Coverage model

Secure Payment Pages support the same 8 networks as Request API destinations:

| Type    | Networks                                                                                       |
| ------- | ---------------------------------------------------------------------------------------------- |
| EVM     | Ethereum (`mainnet`), Arbitrum One, Optimism, Base, Polygon (`matic`), BNB Smart Chain (`bsc`) |
| Non-EVM | **Tron**                                                                                       |
| Testnet | Sepolia                                                                                        |

Stablecoins (USDC, USDT) are supported on every mainnet, including **Tron** (USDT and USDC, TRC-20). **USDT0** is additionally available as a payment currency (an alias of USDT) on Arbitrum One, Optimism, and Polygon. FAU is available on Sepolia for testing.

For a payer's perspective, a Secure Payment link can be paid from any of these chains — when the source chain differs from the merchant's destination chain, the swap is routed through Li.Fi (EVM source chains only; Tron payments are same-chain).

<Warning>
  Batch secure payment links — multiple payees in a single hosted link — are EVM-only. Tron Secure Payment links are single-recipient.
</Warning>

For the canonical chain × currency table and feature-support matrix, see [Supported Chains and Currencies](/resources/supported-chains-and-currencies).

## Supported currencies

Currencies are determined by the Request token list and available per network.

Use `GET /v2/currencies` to query support by network.

<RequestExample>
  ```bash cURL theme={null}
  curl -X GET "https://api.request.network/v2/currencies?network=sepolia" \
    -H "x-api-key: YOUR_API_KEY"
  ```
</RequestExample>

<ResponseExample>
  ```json Example theme={null}
  [
    {
      "id": "FAU-sepolia",
      "name": "FAU",
      "symbol": "FAU",
      "decimals": 18,
      "network": "sepolia",
      "type": "ERC20",
      "chainId": 11155111
    }
  ]
  ```
</ResponseExample>

## How to verify support

* Query `GET /v2/currencies` with `network` and `symbol` filters for discovery
* Validate currency IDs before calling `POST /v2/secure-payments`
* Use the same network and currency validation rules you apply to normal request flows

<Info>
  For an at-a-glance list of ecosystem support, see [Supported Chains and Currencies](/resources/supported-chains-and-currencies).
</Info>

## Preflight checklist

* Confirm each currency ID exists in `GET /v2/currencies`
* Confirm each request network is supported by your target flow
* Confirm your selected currencies are available on those networks