One API to orchestrate every cross-border route

Any source in, any destination out.

Get startedAPI docs

One integration for every route.

How it moves

One payment, every cross-border route

Money comes in from any source. Nodu picks the rail, the FX and the checks, carries it across the border and pays out to any destination.

  • Bank account
  • Crypto wallet
  • Held balance

RouteFXChecks

  • Any bank
  • Any wallet
  • Partner payout
The dashed line is the border. Nodu crosses it on stablecoin rails in about 60 seconds, with no correspondent banks and no pre-funded accounts.

$1,000,000

£
¥
€
$
EURUSDCUSD

Any source

Bank account, crypto wallet or a balance you hold.

Start a payment from wherever the money is. When it has to be paid in by your customer, Nodu hands you the deposit details and takes over the moment the funds land. Start it from a balance you hold instead, and there is nothing to wait for.

Get started

40+ currencies

Any destination

Any account, on any rail Nodu supports.

Deliver to the customer’s own account, to a third party you have saved, or into a wallet with Nodu. The rail and currency follow from the destination itself, and a reference travels with the payment wherever the rail carries one.

See the destinations
$10,000€10,842

FEE 0.05%

Priced first

Lock the price before the money moves.

Ask for a quote and Nodu fixes the rate and every fee for 15 minutes. Send the payment with that quote and the amount your customer saw is the amount that arrives, or the payment does not go.

Get FX access

The route

Fiat in. Stablecoin moves it. Fiat out.

Money lands, converts to stablecoin where the corridor needs it, crosses the border in minutes without correspondent banks or pre-funded accounts, and converts back to local currency on delivery. On fiat-to-fiat routes, your users only ever see fiat.

*On fiat-to-fiat routes, sender and recipient only see fiat.

Fiat in

Stablecoin moves it

Fiat out

$

EURUSDCBRL

10,000 EUR

Sender's bank · Berlin

$58,420 BRL

Recipient's bank · São Paulo

How it works

Quote, send, watch. One object moves through one clear set of steps, and pauses only when a check needs the customer.

Get startedCalculate fee

  • One direction only

    A payment moves from awaiting funds to delivered and never turns back. When it is done, it is done, and you know exactly where it ended.

  • Pauses that resolve themselves

    If a check needs a second look, or a customer has to confirm a wallet is theirs, the payment waits, then carries on the moment that is settled. No call from you.

  1. Quote

    Name the source, the destination and either the amount to send or the amount to receive. Nodu returns the full breakdown, locked.

  2. Send

    Create the payment with that quote. Send an idempotency key with it, so a retry can never create a second payment.

  3. Follow

    Subscribe to notifications and every change reaches you with the whole payment attached. No polling, no follow-up calls.

Who orchestrates on Nodu

Built for the teams that move money for others

Fintechs, PSPs, payroll platforms and exchanges keep one integration and let Nodu decide how each route is executed.

Trust

Compliance inside the flow, not bolted on.

Nodu operates through licensed and registered group entities in the EU and Canada. Screening, reviews and wallet ownership checks happen inside the payment itself, and it resumes on its own once they are done.

  • MiCA + PI - Latvia (EU-wide)
  • MSB - Canada (FINTRAC)

40+

Currencies & Stablecoins

Platform

One REST API, with a sandbox that stands in for the money.

A real payment waits on two things the API cannot produce: the customer’s funds and their proof of a wallet. In the sandbox, both are simulated, so the whole route runs end to end before anything real moves.

Get API accessAPI docs

FAQs

Cross-border payment orchestration routes an international payment through one integration. It picks the source, the rail, the currency conversion and the compliance checks, then moves the money from payer to recipient across borders. One API covers every corridor, so you do not build or maintain a separate connection for each one.

The building blocks

Every primitive orchestration composes

One integration wires these together. Each is a page of its own.

Guides to payment orchestration

All guides

Ready to run every corridor through one integration?

Apply for access and read the API docs. Both take minutes.

Get startedAPI docs