On this page
Supported Currencies
Check which of the 13 blockchain networks support USDT, USDC, USD1, DAI, and gold-backed XAUT before enabling assets in a project.
Request fields
currency is a unified public API field. It can contain either a fiat currency code such as USD or a crypto asset symbol such as USDT.
For fiat invoices, send currency without network:
{
"amount": "100.00",
"currency": "USD"
}
For direct crypto invoices and withdrawals, send currency with network:
{
"amount": "50.00",
"currency": "USDT",
"network": "TRC20"
}
Withdrawals support crypto assets only, and are limited to USDT and USDC — each on any network where that token is issued (see the matrix below).
network — when creating a direct crypto invoice or withdrawal, specify currency together with network:
{
"currency": "USDT",
"network": "TRC20"
}
Valid network values: TRC20, ERC20, BEP20, POLYGON, ARBITRUM, OPTIMISM, BASE, TON, AVAX, SOL, NEAR, SUI, PLASMA.
Pricing model
With fiat pricing (currency = USD/EUR/…), Paymos locks the FX rate at the moment the customer picks a token + network on the hosted checkout. The customer then pays the equivalent stablecoin amount. The locked rate is returned on the invoice as payment.exchange_rate.
With direct crypto pricing (currency = USDT/USDC/… with network), the customer pays the exact amount in that token on that network. No FX involved.
Settlement is always in the stablecoin the customer paid with. Paymos never converts crypto to fiat: you withdraw the same stablecoin to your own wallet, and any conversion to fiat is something you arrange yourself, off Paymos.
Fiat currencies
| Group | Codes |
|---|---|
| Major | USD, EUR, GBP, CHF, CAD, AUD, NZD, JPY |
| Europe | PLN, CZK, DKK, SEK, NOK, HUF |
| CIS | RUB, UAH, GEL |
| Asia | CNY, HKD, KRW, INR, IDR, MYR, PHP, THB, VND, PKR, SGD, BDT, LKR, MMK, TWD |
| Americas | BRL, MXN, ARS, CLP, BMD, VEF |
| Middle East / Africa | TRY, AED, ILS, NGN, ZAR, BHD, KWD, SAR |
Tokens
| Token | Symbol | Networks |
|---|---|---|
| Tether USD | USDT |
TRC20, ERC20, BEP20, POLYGON, ARBITRUM, OPTIMISM, TON, AVAX, SOL, NEAR, PLASMA |
| USD Coin | USDC |
ERC20, BEP20, POLYGON, ARBITRUM, OPTIMISM, BASE, AVAX, SOL, NEAR, SUI |
| Tether Gold | XAUT |
ERC20 |
| Dai | DAI |
ERC20 |
| World Liberty USD | USD1 |
ERC20, SOL |
Networks
Paymos waits for network-appropriate finality before crediting a payment. On most chains the required depth scales with the payment's USD amount — small payments confirm fast, large ones wait longer. Chains with fast native finality (BNB Smart Chain, Polygon, and Solana) use the chain's finalized tag instead of a block count. Exact confirmation depths are operational and can change without notice; the value applied to each payment is returned as required_confirmations in API responses, and is null when the chain confirms by finality rather than a fixed block count.
| Network | Code | Type |
|---|---|---|
| Tron | TRC20 |
L1 |
| Ethereum | ERC20 |
L1 |
| BNB Smart Chain | BEP20 |
L1 |
| Polygon PoS | POLYGON |
L1 |
| Arbitrum One | ARBITRUM |
L2 |
| Optimism | OPTIMISM |
L2 |
| Base | BASE |
L2 |
| TON | TON |
L1 |
| Avalanche | AVAX |
L1 |
| Solana | SOL |
L1 |
| NEAR | NEAR |
L1 |
| Sui | SUI |
L1 |
| Plasma | PLASMA |
L1 |
Token-network matrix
Not every crypto asset is available on every network. The table below shows all valid combinations:
| TRC20 | ERC20 | BEP20 | POLYGON | ARBITRUM | OPTIMISM | BASE | TON | AVAX | SOL | NEAR | SUI | PLASMA | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| USDT | Yes | Yes | Yes | Yes | Yes | Yes | -- | Yes | Yes | Yes | Yes | -- | Yes |
| USDC | -- | Yes | Yes | Yes | Yes | Yes | Yes | -- | Yes | Yes | Yes | Yes | -- |
| XAUT | -- | Yes | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| DAI | -- | Yes | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| USD1 | -- | Yes | -- | -- | -- | -- | -- | -- | -- | Yes | -- | -- | -- |