RECRYPBack the layer above every sovereign rail — before it's obvious.
We're pre-seed and building in stealth. This page is for two audiences: institutional investors evaluating the thesis early, and institutional treasuries evaluating direct settlement access once we're live. Both are conversations we want to have now, not after the fact.
Every sovereign is solving its own problem. Nobody is solving the layer between them.
Every central bank issuing a CBDC is solving a domestic problem: faster settlement, financial inclusion, monetary policy control, resilience against private stablecoins. None of them are incentivized to solve interoperability with every other sovereign's rail — that's not their mandate, and it isn't going to be solved by any single sovereign acting alone.
That's a job for a neutral infrastructure layer, and at the scale this will eventually require, it doesn't exist yet. The correspondent banking system SWIFT sits on top of took decades to build network effects around. The sovereign digital currency era is starting now, while the equivalent interoperability layer is still unclaimed. That's the window we're building in.
We think the winning position is structurally neutral: not a competing currency, not built on speculative crypto assets, and not owned by any single sovereign or big-tech platform that another sovereign would hesitate to depend on.
What we think makes this defensible.
Market timing
130+ countries, representing an estimated 98% of global GDP, are already exploring or piloting a CBDC. None of them have solved cross-border interoperability, and no obvious incumbent — not SWIFT, not a card network, not a competing sovereign — is structurally positioned to be the neutral layer between them.
Defensibility
Interoperability infrastructure compounds: every additional corridor connected makes the network more valuable to the next central bank considering a connection, and early regulatory sandbox relationships are difficult for a later entrant to replicate quickly.
Position
We don't issue currency, don't compete with any sovereign, and aren't built on speculative crypto assets — which is precisely what makes this palatable to the institutions who'd otherwise never adopt a private-sector rail.
Stage, honestly
We're pre-seed, building in stealth, and prioritizing depth of thesis and first regulatory relationships over speed of announcement. There's no traction to overstate here — this is an early conversation, and we'd rather have it straight.
Direct settlement access, once a corridor is live.
Separate from the investment thesis: treasuries get the same settlement access commercial banks and PSPs do — direct exposure to sovereign digital currency corridors without routing capital through a legacy correspondent chain.
Intercompany transfers without local accounts everywhere
A treasury settles intercompany transfers across three jurisdictions without maintaining a local bank account and pre-funded balance in each one.
Programmatic FX exposure management
A treasury manages FX exposure across sovereign currency pairs programmatically, instead of negotiating rates bilaterally with each banking relationship.
Direct exposure without OTC counterparty risk
An institutional treasury gains direct settlement exposure to a sovereign digital currency corridor without the counterparty risk of an OTC crypto desk.
From investors and treasury teams.
Are you raising right now?
We're pre-seed and talking with investors who share the thesis early. Reach out and we'll share where things stand.
What's the business model?
Infrastructure-layer economics — the specific mechanics are part of what we're finalizing at this stage, alongside the architecture itself. Happy to walk through our current thinking directly rather than posting a placeholder answer here.
Isn't this dependent on central banks actually adopting CBDCs at scale?
Yes — that's the bet. 134+ countries are already exploring or piloting one; we think the interoperability layer is the more durable and less contested part of that build-out, regardless of which specific CBDCs ultimately win adoption.
How is this different from stablecoin infrastructure plays?
Stablecoin infrastructure connects private, typically dollar-denominated tokens. We're built specifically for sovereign-issued digital currencies and their cross-currency interoperability — a different, and largely unaddressed, problem.
Why is now the right timing for this thesis, not five years too early?
134 countries — about 98% of global GDP — are now exploring or piloting a CBDC, per the Atlantic Council's tracker, with 70+ already in development or live pilot. The UAE's Digital Dirham went live for retail use in March 2026 with cross-border capability already switched on. SWIFT finished its core ISO 20022 migration in November 2025. mBridge processed over $55B before BIS's 2024 withdrawal exposed the governance gap in multilateral bridges. None of that was true three years ago, and none of it required Recryp to exist for it to happen — the rails are being built regardless. The open question is who builds the layer connecting them, and that window is open now, not in five years.
What's the actual size of the opportunity?
McKinsey's Global Payments Map puts total cross-border payment flows at roughly $179 trillion, with B2B cross-border alone projected to exceed $42.7 trillion in 2026. None of that volume has a common settlement layer across sovereign digital currencies today — it's not a market Recryp has to create from nothing, it's an existing flow currently forced through correspondent banking that a CBDC-native settlement layer can intercept as issuance scales.
Further reading: the interoperability glossary and Insights hub.
Investor or treasury — talk to us early.
Tell us which side you're approaching from — we'll route the conversation accordingly.