Stablecoin & digital-asset infrastructure
soonish is a software studio for regulated fintech. We build exchange engines, non-custodial wallet infrastructure and stablecoin settlement, plus the reconciliation that keeps an auditor satisfied.
Custody exists in one step of six, for minutes, by design. Then the asset is swept to a wallet the customer holds and the platform's own balance is back to zero. Everything else in finance settles soonish; this is the part that shouldn't.
Building and running regulated brokerages and exchanges
Client money held on the platform's balance sheet, by design
From signed scope to a documented, production handover
Execution cost target once internal flow is netted first
Capabilities
We don't take general software work. Every engagement is one of these, or a combination, because that's where a decade of regulated market-infrastructure experience is worth paying for.
01 · Execution
RFQ across liquidity providers polled in parallel, with failover and firm
quotes held long enough to be honoured. Best-execution evidence you can
hand a regulator, and a single price to the customer: no order book, no
charts, price = execution.
02 · Wallets
MPC key management with no seed phrase and no company-held share, so the balance you'd have to defend in an incident is zero and publicly verifiable. Plus recovery flows, so self-custody doesn't mean twenty-four words on a customer's kitchen table.
03 · Settlement
Convert on arrival, sweep in minutes, convert back in flight. On- and off-ramps wired to real fiat rails, so the platform never has to sit on customer money just to function.
04 · Netting
Match internal flow at mid before anything reaches a provider. Thousands of recurring orders collapse into one execution, and provider cost drops by an order of magnitude. See the worked example.
05 · Ledger
Double-entry, multi-currency, multi-entity, with balances derived from entries rather than stored and hoped for. Every state change logged and every position reconcilable against both the provider and the chain.
Execution · Internalisation
Recurring buys are the easiest flow in fintech to execute badly. Sent to market one by one, a scheduled-purchase book pays a provider spread on every order. Matched internally first, most of that turnover never leaves the building.
Worked example · one recurring-order window
5,000 buys against 200 sells, batched into a single execution instead of 5,200 round trips.
Buyers matched against sellers at the mid price. Both sides get a fair fill and neither pays a provider for it.
Down from the tens of basis points a naive order-by-order implementation pays away.
Current work
Client names stay private until our clients launch. Here's what the work looks like.
Money goes in, converts the moment it arrives, and lands in a wallet that belongs to the customer rather than to the company. The client owns the brand and the licence; we're building the engine underneath it.
An MPC wallet with no seed phrase and no key share held company-side. Assets pass through a settlement window measured in minutes, and the company's own balances are publicly verifiable at zero.
No fiat held at any point. Every deposit converts on arrival and sweeps straight to the customer's wallet; withdrawals convert back in flight to a bank account.
Goals, automatic recurring purchases and the habit that comes with them, behind an interface that behaves like a bank rather than an exchange.
Stack
We don't rebuild what a regulated provider already does better. These are the ones we know well enough to wire, monitor and reconcile against without a discovery phase.
Custody & keys
Fireblocks
MPC wallet infrastructure, policy engine and transfer signing.
Wallets & auth
Dynamic
Embedded wallet creation and sign-in without a seed phrase.
Fiat rails
Fiat Republic
Banking and payment rails built for licensed crypto platforms.
Card acquiring
Checkout.com
Card deposits, 3DS and the failure modes that come with both.
Accounts & FX
OpenPayd
Embedded accounts, named IBANs and multi-currency conversion.
Liquidity
Stillman Digital
Digital-asset OTC execution as one leg of the RFQ panel.
Process
Value dates, not vibes. This is the schedule we hold ourselves to, measured from the day the scope is signed.
Forty-five minutes. You walk us through the money flow, we tell you what's hard and what isn't. You leave with a written scope either way.
Running in your stack against provider sandboxes, with the nasty edge cases already wired. Not a clickable mockup.
Live with real money at capped volume, full audit trail, your engineers in the codebase alongside ours.
Documented, tested and yours. We stay on retainer if you want us, and get out of the way if you don't.
Studio
Built by people who've run regulated market infrastructure, and learned what breaks when it isn't built this way.
Two to four engineers who have shipped regulated market infrastructure before. Nobody sits between you and the people writing the code.
Every state change logged, every balance derivable, every execution evidenced. We build for the version of your company that has a regulator, because it's coming.
TypeScript, Go, Python, Postgres: whatever your team already runs and can maintain after we leave. We're not selling you a platform.
Reply within 1 business day
Six fields. An engineer reads it, not a form router, and you get a straight answer about whether we're the right studio for the job.
Prefer email? hello@soonish.llc