Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Welcome

Understanding orda

Developers use orda to submit an intent (e.g., “swap 1,000 USDC → BRZ”) and the network finds the best execution through competing solvers.

The orda network is the coordination layer that makes global value movement efficient:

  • Intents: Developers define what they want.

  • Solvers: Competing participants fulfill those intents at the best price.

Why orda exists

Moving value today is fragmented. The same value can cost anywhere between 0–300 bps to transfer, depending on who you are and how you connect:

Market Segment
Typical Fees
Access Mechanism
Settlement Time

Tier 1 Interbank

0–8 bps

Bilateral

T+0

Institutional

12–18 bps

Prime Broker

T+0 – T+1

Corporate Treasury

16–50 bps

Bank Desk Markup

T+0 – T+2

Processors

25–70 bps

Aggregator RFQ

T+1 – T+3

Retail / SME

100–300+ bps

Card Networks & Bank Rails

Instant – T+3

Different participants pay radically different spreads for the same movement of value, because of float fragmentation and layers of intermediaries.

How orda changes it

orda collapses this complexity by acting as a coordination layer:

  • Unified access: One integration to reach banks, blockchains, and stablecoin systems.

  • Solver competition: Multiple counterparties compete to fulfill each intent, compressing spreads toward interbank levels.

  • Vaults: Shared liquidity replaces pre-funding, making float productive and settlement faster.

Instead of multiple pricing tiers, developers get a single fair price, all from a single interface.

Whether you’re building an exchange, wallet or payments app, orda abstracts the mess of FX and liquidity into a single priced, programmable layer.

Use Cases

Move value between fiat and stablecoin corridors at competitive spreads.

Example scenarios:

  • Remittance platforms sending USD → BRL in real-time

  • Treasury desks converting USDC → BRL for local operations

  • Marketplaces settling payouts to sellers across borders

How to build it:

  • Use the API or SDK to integrate quickly

  • Generate wallets for settlement flows

  • Create recipients with bank or crypto details

  • Begin quoting FX intents and fulfill at best price

Embed on/off-ramping into your app with a few lines of code.

Example scenarios:

  • Wallets adding local bank deposits/withdrawals

  • Exchanges offering direct top-ups

  • Fintech apps letting users buy stablecoins instantly

How to build it:

  • Create a Recipient with bank or crypto settlement details

  • Request a quote and pass it to the end user to execute

  • Use the widget for plug & use

Unify fragmented liquidity across blockchains and stablecoins.

Example scenarios:

  • Swap USDC on Ethereum → BRZ on Base

  • Bridge AUSD from Plasma → Solana

  • Build network & currency abstracted apps with intent-based routing

How to build it:

  • Use the API or SDK for cross-chain swaps

  • Or embed the Widget for a drop-in swap UI

  • Let solvers compete for best execution across chains

Push beyond basic flows with primitives that unlock infrastructure-level use cases.

Example scenarios:

  • On-chain liquidity management: Borrow from vaults, rebalance float and monitor utilization without fragmented pre-funding

  • Chain-abstracted infrastructure: Submit one intent and let solvers handle routing across chains and assets

  • Unified balances: Power wallets with a single spendable balance (fiat + stablecoins + chains), bridging abstraction but extended to banks.

  • Solver strategies: Run custom solver bots to capture spreads, arbitrage across corridors, or internalize margins as a PSP

Get started

NextWho is an orda solver?

Last updated