United Digital Settlement Rail

One API for every currency, token and corridor.

Connect one endpoint and settle across fiat, stablecoins and tokenized assets — atomically, with compliance and proof of reserve built in. No card networks, no per-corridor bank integrations. Live in minutes.

No setup call required · test keys work instantly · corridors added by config
settle.shresponse
# one call: pay in one asset, settle in another curl -X POST https://api.urail.io/api/pay \ -H "X-UR-KEY: uk_live_..." \ -d '{ "from": "acct_amina", "to": "merchant_dubai", "pay_asset": "NGN", // naira in "settle_asset": "AEC", // dirhams out "amount_usd": 45.00 }'
200 OK settled in 0.8s · atomic · compliance ✓ · anchored { "tx": "tx_9f3a…", "status": "COMMITTED", "proof": "/api/proof/…" }
Atomic multi-asset settlement Compliance before money moves Proof of reserve on demand Merkle-anchored on Universa Fiat · stablecoins · tokenized assets
Connect the rail

Three steps to your first settlement.

The app you build talks to one API. Everything underneath — banks, the stablecoin issuer, custody, compliance, reconciliation — is the rail's job, not yours.

1

Get your keys

Sign in and generate an HMAC key pair. Test keys settle against a live sandbox instantly — no onboarding call, no waiting.

2

Make one call

One signed POST /api/pay — name the asset in, the asset out, and the amount. The rail resolves the FX, screens compliance, and settles atomically.

3

Settle & prove

You get a committed transaction and a verifiable proof. Your users see one payment; your finance team gets net positions and proof of reserve.

quickstart.js
const ur = new URail("uk_live_..."); // top up a user in naira → they hold dirhams await ur.topup({ account: "acct_amina", pay_asset: "NGN", amount: 50000, credit_asset: "AEC" // AECoin, 1:1 AED }); // later, they spend at a UAE merchant await ur.pay({ from: "acct_amina", to: "merchant_dubai", settle_asset: "AEC", amount: 45 }); // merchant is paid real dirhams. done.

You write ~10 lines. The rail does the rest.

Behind those two calls: a Nigerian bank collection, an NGN→AEC swap, a regulated mint through the stablecoin issuer, a user balance, a merchant redemption, and a UAE-bank payout — all reconciled and provable.

  • No card network, no interchange
  • No separate bank integration per corridor
  • Compliance screening runs before settlement
  • Every balance backed 1:1, proof on demand
  • SDKs for Node, Python, and plain REST
Corridors

Live corridor: Nigeria → UAE.

A user tops up in naira and spends dirhams in Dubai — one balance, real dirhams at the till. Add any corridor the same way: register the assets, set the route.

₦ NGN
Top up in Lagos. Naira settles into the partner bank's escrow — custody stays local.
U:RAIL
Swap & mint. NGN→AEC, regulated AECoin minted via AED Stablecoin LLC, credited to the user.
د.إ AEC
Spend in Dubai. The user pays a merchant in dirhams; AEC Wallet redeems to real AED in a UAE bank.

Two fiat ends. A regulated coin between them.

The naira never leaves Nigeria; the dirhams are born in the UAE. U:RAIL is the connective layer that makes the two sides one atomic, compliant, provable transaction — the part no single bank or stablecoin holds.

→ Run the corridor demo, first as the customer, then as the settlement bank.

See the corridor live
Why a rail, not two banks and a coin

The work you don't have to build.

A bank on each side plus a stablecoin can move one payment. They share no common ledger — and that gap is exactly what a settlement rail is for.

Atomicity

One transaction, not two systems

Debiting fiat on one side and minting the coin on the other are two actions in two systems. Between them, funds sit in limbo. On the rail they commit together or not at all — no limbo, ever.

Compliance

Screening over the whole route

Each party sees only its own leg, so risk hides in the seam between the two sides. The rail screens the entire route before settlement — a blocked payment never reaches the ledger.

Reserves

One provable book across both sides

No single participant holds the corridor's net position or proves that every unit issued is backed on the other side. The rail does — on demand, with a tamper-evident audit trail.

Integration

One connection, every corridor

Go direct and each new corridor is a fresh pair of bank integrations. Connect the rail once and add corridors by config — the way Stripe abstracts card networks, for settlement.

Live demos

Not a mockup. The real engine.

Every track runs against the actual settlement engine — balances move, compliance verdicts fire, proofs verify. Start with the Nigeria→UAE corridor.

1 API
every asset & corridor
<1s
atomic settlement
pre-
settlement compliance
1:1
proof of reserve

Connect the rail. Settle anything.

Get test keys and make your first cross-asset settlement in minutes — then watch it prove itself on the live demos.