Anything in.Anything out.One API.
Every payment is a routing problem. Figo picks the rails, settles through dollars, and delivers in 122 markets. The routing is the product.
Moving money isn't hard. Choosing how is.
Every corridor is its own project: its own contracts, settlement windows, failure modes, and often different rails in than out. Add a market and you start again.
- money
- a bank
- an FX desk
- a card processor
- another processor
- customer
- money
- figo
- delivered
Collect and payout are separate primitives. The router pairs them.
The dollar hub is the routing engine: it picks the path before your quote locks. No corridor matrix, just a source and a destination.
Collect
Take bank transfers, mobile money, or stablecoins. Funds land as dollars the same day.
Route
One request pairs any source with any destination. The router weighs rails, liquidity, and cost, then locks the quote.
Pay out
Send local currency or crypto to any supported market. The rate you accept is the rate that executes.
Stablecoins aren't the product. They're the settlement layer. Dollars are just the best hub to route through.
Watch a movement run.
Pick an amount and a pairing. The run is simulated; the stages are the ones the timeline returns.
Four engines between your request and the rails.
The API is thin on purpose. The work happens underneath, and none of it leaks into your integration.
122 payout markets. 15 collection markets. One dollar balance.
On mobile-money rails a single payout caps out at a few hundred dollars, so $100M of flow is hundreds of thousands of payouts, not one wire. We built the router for that shape; send us your corridors and we'll map them method by method.
Infrastructure you can put in front of a compliance team.
Segregated, prefunded balances, verifiable on-chain. Credit is never quietly bundled into a quote. We stand behind execution contractually.
Wire two endpoints, not fifty corridors.
Sandbox keys on day one; idempotent writes, webhooks on every state change, and recipes for the common flows. You should reach your first movement without talking to us.
This isn't a spec sheet: the consumer Figo app runs on the same API you get. When settlement slows somewhere in the world, we feel it before you do. Here's what actually happens during a payout, alongside the rest of our engineering writing.
POST /v1/orchestrate
{
"source": { "kind": "fiat", "currency": "NGN" },
"destination": { "kind": "crypto", "asset_id": "btc-bitcoin" }
}
# the response is the state machine
HTTP 201
{
"id": "orch_8Yq3K2",
"status": "awaiting_payin",
"pay_in": { "bank_info": { … } }
}
Money moves.We decide how.
Every year adds another rail, and none of them replace the others. They accumulate, and the integration burden compounds.
The durable layer is the one that chooses: rails become interchangeable under a router, the way servers did under a load balancer. That is the layer we are building, and dollars are its clearing house.
Build on the routing layer.
Sign up, grab sandbox keys, and send a test movement this afternoon. If you'd rather walk through your corridors with a human first, book a call.