Every payment takes the best route

Transfer Routes reads destination, urgency, and cost, then routes across SWIFT, US rails, stablecoins, and FX automatically.

Book a demo View docs

One instruction2,000,000.00 USD → BRL · same day

Every eligible path scoredSpeed · all-in cost · reliability
Screened once for the whole routeOne vetted counterparty, whichever legsCleared

USDC → FX → PixAbout 2 hours · chosenIn flight
Direct SWIFT wire2 to 3 days · correspondent deductions

NO RAIL IN THE REQUEST · THE ROUTE COMES BACK ON THE PAYMENTILLUSTRATIVE ROUTE

01
Instruction
- One instruction2,000,000.00 USD → BRL · same day
02
Routing
- Every eligible path scoredSpeed · all-in cost · reliability
- Screened once for the whole routeOne vetted counterparty, whichever legsCleared
03
Route chosen
- USDC → FX → PixAbout 2 hours · chosenIn flight

NO RAIL IN THE REQUEST · THE ROUTE COMES BACK ON THE PAYMENTILLUSTRATIVE ROUTE

Who it’s for

Transfer Routes is the routing layer of Infinite 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.

Companies moving volume across borders that hand-pick rails corridor by corridor today.
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.

The network

Internet highways for money.

Infinite is the global financial network built on a compliance system of intelligence; the more companies that connect, the faster and cheaper every dollar moves.

Vetted once, trusted everywhereScreening 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 routesEvery 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 timeRouting learns from every payment on the network. As volume grows, corridor data gets sharper and the best path gets better for every member.

How it works

How routing picks a rail.

Routing is deterministic: the route comes back on the payment object.

Read the instruction

Destination country and currency, amount, urgency, and cost preference. 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.

Worked example

One instruction. $2M, USD to BRL, same day.

The instruction

Amount: $2,000,000.00 USD
Destination: Supplier account · São Paulo, Brazil (BRL)
Urgency: Same day
Rail: Not specified: routing decides

Routes evaluated · USD/BRL mid 5.4210

SWIFT correspondent wireUSD → correspondent chain → BRL

Settlement2–4 business days

Est. all-in cost$10,045

Recipient getsR$ 10,787,800

Considered

Fedwire + local FX providerUSD → Fedwire → FX partner → BRL

Settlement1–2 business days

Est. all-in cost$6,180

Recipient getsR$ 10,809,400

Considered

Stablecoin + network FXUSD → USDC → FX → BRL via PIX

Settlement~2 hours · 24/7

Est. all-in cost$2,410

Recipient getsR$ 10,829,000

Selected

R$ 41,200more delivered vs the SWIFT route

2–4 days → ~2 hrssettlement, including the FX leg

One payment objectone status stream, one ledger entry

Illustrative figures: rates, fees, and times vary by corridor and counterparty.

Developers

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.

Read the docs

transfer.tsIllustrative example

// 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',
});

response.json

// 201 Created. Route chosen and counterparty screened on one instruction.
{
  "id": "pay_9c4d1e", "status": "in_flight",
  "amount": "2000000.00", "currency": "USD", "destination": "acct_br_9034",
  "route": {
    "legs": ["transfer:usdc", "fx:usdc-brl", "payout:pix"],
    "estimatedSettlement": "~2 hours", "cost": "quoted"
  },
  "compliance": {
    "case": "case_6a8f2b", "outcome": "cleared", "policy": "pol_2f7e",
    "checks": [
      { "type": "sanctions", "result": "clear", "evidence": "evd_31ab" },
      { "type": "kyb", "result": "clear", "evidence": "evd_08c2", "reused": true }
    ]
  }
}

FAQ

Answers before you ask

Do I choose the rail?

By default, no. 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.

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.

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 Stablecoin 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.

See the companies processing on Infinite

Watch a payment pick its route.

Bring your hardest corridor. 30 minutes: the path, the cost, and the settlement time, next to what you pay today.

Book a demo

Ask an AI about Transfer RoutesChatGPT ClaudePerplexity Gemini