Company
We're building the settlement layer for money that doesn't move in dollars.
Thirty-six currencies. Six hundred and thirty direct pairs. One technology layer over licensed rails.
The problem
Currency was never a business decision. It was plumbing wearing a commercial disguise.
You don't invoice in zloty because your bank doesn't settle zloty. You quote in dollars — not because the deal is in dollars, but because dollars are what your rail speaks. Your customer eats the conversion, or you do — either way it comes out of the margin.
Adding a currency today means a banking relationship, a local entity, a compliance review, and a pre-funded account that strands your capital. That's not infrastructure. That's procurement.
The mission
Currency should be a parameter.
Nine months of procurement, or a string. That's the whole difference, and it's the entire company. No entity, no relationship, no pre-funding, no project — the currency stops being a constraint you plan around and becomes a field you fill in.
Adding a currency · before
- Bank relationship3–9 months
- Local entityRequired
- Pre-funded accountCapital stranded
- Compliance reviewQuarterly, forever
Adding a currency · on a layer
{ "to": "TRY" }- Settlement in minutes, not days
- One spread, quoted before you commit
- Programmatic, via one API
A licence is a permission with edges. Software is what you put on top of everyone else's edges.
Check your pair.
If we can't do it, we'll tell you on the call, not in month three.