Remitflex Documentation

Before you create a payment link or payment route, check what Remitflex supports. Responses use network names and token symbols — not chain IDs or contract addresses. Scope: api:read For the full curated table, see Corridor matrix.

One call is enough

curl https://api.remitflex.io/v1/payment-routes/chains \
  -H "Authorization: Bearer $REMITFLEX_API_KEY"

Returns three things:

Field	What it answers
`origins`	Networks payers can send from, with accepted `tokens`
`settlements`	Where you receive — Base (USDC, USDT) or Solana (USDC, USDT, EURC)
`routing`	For each origin token, which settlement networks and tokens work

Payment links use the same shape at /collections/chains.

Prefer /chains over /corridors or /currencies — those return overlapping data. Call discovery at runtime for the live matrix.

Example response (abbreviated)

{
  "origins": [
    { "key": "bitcoin", "network": "Bitcoin", "addressFormat": "bitcoin", "tokens": ["BTC"] },
    { "key": "tron", "network": "Tron", "addressFormat": "tron", "tokens": ["USDT"] },
    { "key": "bnb", "network": "BSC", "addressFormat": "evm", "tokens": ["BNB", "USDT", "USDC"] },
    { "key": "polygon", "network": "Polygon", "addressFormat": "evm", "tokens": ["USDC", "USDT", "USDC.e"] },
    { "key": "ethereum", "network": "Ethereum", "addressFormat": "evm", "tokens": ["USDC", "USDT", "ETH"] },
    { "key": "base", "network": "Base", "addressFormat": "evm", "tokens": ["USDC", "USDT", "ETH"] },
    { "key": "solana", "network": "Solana", "addressFormat": "solana", "tokens": ["USDC", "USDT", "EURC", "SOL"] }
  ],
  "settlements": [
    { "key": "base", "network": "Base", "addressFormat": "evm", "tokens": ["USDC", "USDT"] },
    { "key": "solana", "network": "Solana", "addressFormat": "solana", "tokens": ["USDC", "USDT", "EURC"] }
  ],
  "routing": [
    {
      "key": "tron",
      "network": "Tron",
      "token": "USDT",
      "settlements": [
        { "key": "base", "network": "Base", "tokens": ["USDC", "USDT"] },
        { "key": "solana", "network": "Solana", "tokens": ["USDC", "USDT"] }
      ]
    },
    {
      "key": "polygon",
      "network": "Polygon",
      "token": "USDC",
      "settlements": [
        { "key": "base", "network": "Base", "tokens": ["USDC"] },
        { "key": "solana", "network": "Solana", "tokens": ["USDC"] }
      ]
    },
    {
      "key": "solana",
      "network": "Solana",
      "token": "USDC",
      "settlements": [
        { "key": "base", "network": "Base", "tokens": ["USDC"] },
        { "key": "solana", "network": "Solana", "tokens": ["EURC"] }
      ]
    }
  ]
}

origins[].tokens can include symbols that are not in routing. Only paths in routing are curated corridors — see Corridor matrix. Use key from origins / routing as originChainKey, and key from settlements as destinationChainKey.

Create a route

POST /v1/payment-routes
{
  "name": "Tron · USDT → Solana · USDC",
  "originChainKey": "tron",
  "destinationChainKey": "solana",
  "destinationCurrency": "USDC",
  "destinationAddress": "YourSolanaWallet..."
}

On Solana you may also settle to EURC when that destination appears in routing.

Next steps

Corridor matrix — full origin → settlement table
Payment links — hosted pay URLs
Payment routes — persistent deposit addresses

Get started

Concepts

Collect

Convert & FX

Local money

Customers & ledger

Integration

Networks and corridors

One call is enough

Example response (abbreviated)

Create a route

Next steps

​One call is enough

​Example response (abbreviated)

​Create a route

​Next steps

One call is enough

Example response (abbreviated)

Create a route

Next steps