Every payment takes the best route
Transfer Routes reads destination, urgency, and cost — then routes across SWIFT, US rails, stablecoins, and FX automatically.
Transfer Routes is the routing layer of Infinite (infinite.net) Accounts. You submit a payment — amount, destination, urgency — and the network selects the best route across SWIFT, US rails, stablecoins, and FX, then executes and reconciles it. You never specify a rail.
- For companies moving real volume across borders who are done hand-picking rails corridor by corridor.
- One integration replaces per-rail logic: routing weighs every eligible path — including multi-leg routes like USDC plus FX — against speed, all-in cost, and reliability.
- Every route — single rail or multi-leg — runs from the same Infinite Account: one compliance review, one integration, one ledger, whichever path the payment takes.
Internet highways for money.
Infinite is the compliance network that makes stablecoins work for global business; the more companies that connect, the faster and cheaper every dollar moves.
Vetted once, trusted everywhere
Screening runs at the network level. A counterparty vetted once is vetted for every member — so routes clear in seconds, not review cycles.
More members, more routes
Every company that joins adds endpoints and corridors to the map. New routes light up for everyone — no integration work on your side.
Faster and cheaper over time
Routing learns from every payment on the network. As volume grows, corridor data gets sharper and the best path gets better for every member.
How routing picks a rail.
Routing is deterministic and observable — the route comes back on the payment object, never a black box.
Read the instruction
Destination country and currency, amount, urgency, and cost preference. That is all a payment needs — the rail is not part of the request.
Enumerate eligible routes
Every path that can reach the destination: SWIFT wires, ACH, Fedwire, RTP, stablecoin transfers, and multi-leg combinations with an FX conversion en route.
Score on speed, cost, and reliability
Expected settlement time including cutoffs and weekends, all-in cost including FX margin and correspondent deductions, and observed corridor performance.
Execute and reconcile
The winning route executes leg by leg. You see one payment object, one status stream, and one reconciled ledger entry — with the chosen route attached.
One instruction. $2M, USD to BRL, same day.
- AMOUNT
- $2,000,000.00 USD
- DESTINATION
- Supplier account · São Paulo, Brazil (BRL)
- URGENCY
- Same day
- RAIL
- Not specified — routing decides
Illustrative figures — rates, fees, and times vary by corridor and counterparty.
No rail in the request.
You describe the payment; the route comes back on the response. Pin a rail only when your policy requires it — otherwise routing decides.
// no rail specified — the route comes back const transfer = await infinite.transfers.create({ amount: '2000000.00', currency: 'USD', destination: 'acct_br_9034', // supplier, São Paulo urgency: 'same_day', }); transfer.route.legs; // ['transfer:usdc', 'fx:usdc-brl', 'payout:pix'] transfer.route.estimatedSettlement; // '~2 hours'
Answers before you ask
Do I choose the rail?
By default, no — that is the point. You describe the payment and routing selects the path. When policy requires a specific rail, you can pin one on the request and routing constrains itself to it. For the broader pattern of routing payments across rails behind one integration, see the payment orchestration glossary entry.
What does routing optimize for?
Speed, all-in cost, and reliability, weighted by the urgency and cost preference on the instruction. Expected settlement time includes cutoffs and weekends; all-in cost includes FX margin and correspondent deductions; reliability comes from observed corridor performance. The scoring inputs are the ones shown in the worked example above.
Which rails can a route use?
SWIFT wires, ACH, Fedwire, and RTP, stablecoin transfers (USDC, USDT, OUSD, USDG), and FX conversions across GBP, EUR, MXN, and BRL — individually or combined into multi-leg routes. Every company that joins the network adds endpoints and corridors, so new routes light up with no integration work on your side.
How does compliance work on a multi-leg route?
The same way it works everywhere on Infinite: the counterparty is screened before funds move, and the screening result covers the whole route. One vetted counterparty, whichever path the payment takes. Screening runs at the network level, so a counterparty vetted once is vetted for every member — see Global Compliance.
What do I see while a payment is in flight?
One payment object with the selected route attached, one status stream over webhooks as each leg completes, and one reconciled ledger entry when it settles. You never stitch together per-rail statuses, and the route comes back on the response — never a black box. See the documentation for the model behind it.
- SWIFT PaymentsGlobal wires, one integration
- USD PaymentsACH, Fedwire, RTP
- Stablecoin PaymentsUSDC, USDT, OUSD, USDG
- Foreign ExchangeGBP, EUR, MXN, BRL
- Transfer RoutesInternet Highways for Money
Watch a payment pick its route.
Bring your hardest corridor. In a 30-minute demo we will run it through routing and show you the path, the cost, and the settlement time — side by side with what you pay today.