Cross-Border
Move money across borders.
Every transfer carries its own jurisdiction.
Send to 90+ currencies at the mid-market rate. But the rate is the easy part. Every transfer is resolved before it moves: which law governs it, which regulator has authority, which disclosures you're owed, and which settlement rails are permitted on the corridor.
Mid-market rates
The reference rate and the spread are shown side by side before you confirm. The recipient amount is the number that actually lands.
Locked rates
Lock a quote and the price holds for a bounded window. No silent re-pricing between the moment you decide and the moment it settles.
Jurisdiction resolution
LegalOS resolves the governing law, the supervising regulator, and the required disclosures for the exact corridor — on every transfer, not a sample.
Permitted rails only
Local instant rail, SWIFT wire, or stablecoin — the transfer settles only over a method that's legal on that corridor, chosen automatically.
When a corridor closes, the transfer doesn't fail. It re-routes.
Brazil's Resolution 561 closes stablecoin settlement on inbound cross-border flows from October 2026. LegalOS already encodes the rule: a transfer into Brazil that would have settled on a stablecoin rail is resolved to a bank rail instead, automatically, with the reason recorded on the transfer. The jurisdiction layer isn't a compliance afterthought bolted on at the border — it's a step in the pipeline, and it runs before the money moves.
Settlement Rail
Settlement is the product, not the back office.
So the rail is on the page.
Move value in a fiat-referenced stablecoin and it settles at block finality — minutes, not days — with the reserve attestation in force at the time recorded on the settlement, and a LegalOS gate confirming the corridor permits it. When the gate is closed, the transfer re-routes to a bank rail instead of failing.
Every settlement links to its block, its transaction, and the attestation period it relied on. Finality you can point to — not a promise to settle later.
On-chain finality
The rail waits for the confirmation depth that makes a transfer final on the chosen network, then marks it settled with the block and transaction recorded.
Attestation on file
For issuers that publish them, the reserve attestation period in force at settlement time is captured on the record. No attestation, no broadcast.
Jurisdiction gate
LegalOS resolves whether stablecoin settlement is permitted on the corridor under the framework that governs it — MiCA, NYDFS, and others — before anything is broadcast.
Automatic fallback
A closed gate doesn't bounce the transfer. It re-routes to a bank rail, with the framework consulted and the reason written onto the settlement.
"Settled" should mean settled.
A lot of what gets called settlement is a promise to settle later — a net position that clears in a day or two, if nothing breaks. On the stablecoin rail, a settlement is final when the network says it is, and the record carries the proof: the block, the transaction, the attestation period, and the jurisdiction decision. It's the same rail that backs the T+0 line in the trading section — not a separate product, the same one.