Skip to main content
Cross-chain pay-in: payer sends on one network (Bitcoin, Ethereum, Tron, etc.), you receive stablecoins on Base or Solana. Each route gets a persistent depositAddress. Scopes: api:read, api:write For hosted checkout, use Payment links instead. Discover supported networks in Networks & corridors. Full table: Corridor matrix.
Settling Solana EURC ↔ USDC as a collection path is fine for pay-ins. For treasury conversion with rates and a deposit lifecycle, use Swaps.

Endpoints

{paymentRouteId} is the RemitFlex payment route UUID returned by POST or GET /payment-routes.

Create

Use network keys and token codes from Networks & corridors — not chain IDs or contract addresses:
originChainKey and destinationChainKey are required when creating routes or payment links. Remitflex resolves networks internally — customers never send or receive chain IDs. Response includes depositAddress — share with payers on the origin network.

Status

activearchived (via DELETE). Deposits appear in Transactions as kind: payment_route.