Skip to main content
Payment routes let payers send stablecoins on an origin chain and receive funds on a destination chain. Each route has a persistent deposit address and status (active, paused, archived). Ideal for African fintechs collecting USDC from diaspora or global payers and settling to a treasury wallet. Every route is tied to a customer under your organisation. Required scopes: collections:read, collections:write

​
When to use payment routes

  • Cross-chain pay-ins (Ethereum → Solana, etc.)
  • Per-customer or per-invoice collection addresses
  • Platform aggregation before internal ledgering
For same-chain Solana conversion, use Swaps.

​
Create a route

# Explore supported chains and corridors first
curl https://api.remitflex.io/v1/payment-routes/chains \
  -H "Authorization: Bearer $REMITFLEX_API_KEY"

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

curl -X POST https://api.remitflex.io/v1/payment-routes \
  -H "Authorization: Bearer $REMITFLEX_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Supplier collection",
    "originChainId": 792703809,
    "destinationChainId": 137,
    "destinationCurrency": "0x3c499c542cef5e3811e1192ce70d8cc03d5c3359",
    "destinationAddress": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb",
    "customerId": "optional-customer-uuid"
  }'
The response includes depositAddress — share this with the payer on the origin chain.

​
Monitor deposits

# All deposits for your org
curl https://api.remitflex.io/v1/payment-routes/deposits \
  -H "Authorization: Bearer $REMITFLEX_API_KEY"

# Deposits for one route
curl https://api.remitflex.io/v1/payment-routes/{id}/deposits \
  -H "Authorization: Bearer $REMITFLEX_API_KEY"

# Pull latest deposit state
curl -X POST https://api.remitflex.io/v1/payment-routes/{id}/deposits/sync \
  -H "Authorization: Bearer $REMITFLEX_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

​
Manage lifecycle

# Pause / activate / archive
curl -X POST https://api.remitflex.io/v1/payment-routes/{id}/pause \
  -H "Authorization: Bearer $REMITFLEX_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

curl -X DELETE https://api.remitflex.io/v1/payment-routes/{id} \
  -H "Authorization: Bearer $REMITFLEX_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"
Attach a customerId when creating a route (or omit to use your org’s primary customer). Filter the transactions ledger by the same customerId.

​
API reference

Create route

POST /payment-routes

List routes

GET /payment-routes

Deposits

GET /payment-routes/deposits

Chains & corridors

Discovery endpoints