Supported routes
A payment route converts money arriving at one end and pays it out at the other.
This page lists the combinations POST /v1/payment-routes accepts. Anything
outside them is rejected with a validation error naming the offending field.
Route explorer
Below, you will find all the routes we support. You can use the filters to search
for the routes you are interested in. The last column is the type to send when
you create the route.
On-ramp — fiat in, stablecoin out
You choose the fiat currency to receive and the stablecoin and chain to pay out on. We open a deposit account in that currency; whatever lands there is converted and sent to your address.
Deposit currencies
Payout stablecoins
You do not pick the deposit rails — the account accepts whichever the
currency supports, and they are listed in source.paymentRails when you read
the route back.
Off-ramp — stablecoin in, fiat out
You choose the stablecoin and chain to receive and the bank account to pay out to. We open a deposit address; stablecoin sent there is converted and paid out over the rail you name.
Payout currencies and rails
The rail must belong to the currency — this is the pairing most integrations get
wrong, and a mismatch is rejected with a destinationPaymentRail error.
accountOwnerName, bankName, addressLine1, city and postalCode are
required on every off-ramp route.
Chains
Both directions accept these for destinationPaymentRail (on-ramp) and
sourcePaymentRail (off-ramp):
Not every stablecoin is issued on every chain. Send a stablecoin to an address on a chain that does not carry it — or to an address for a different asset — and the funds are generally unrecoverable. Confirm the pairing with us before opening a route on a combination you have not used before.
Before a route will open
Two conditions apply regardless of the combination you pick:
- The company must be activated by AlphaX, or you get
403 COMPANY_NOT_ACTIVE. See the Overview. - Payment routes must be enabled for the company, and off-ramp is enabled
separately from on-ramp — either being off gives
403 FEATURE_NOT_ENABLED.

