Your clients’ treasury shouldn’t be public
Confidential settlement for client flows. Full visibility for your compliance team.
What a competitor can chart today
USDC, millions
Nothing to chart
The payments aren’t linkable to you.
Burn, runway and a fresh raise, readable before any announcement. Values are illustrative.
Built to be checked
Private, not unaccountable. How the compliance model works
What a public treasury leaks
All of it is readable from one public address, by anyone, for as long as the chain exists.
- Payroll Headcount and salary bands.
- Suppliers Who they buy from, and on what terms.
- Balances Cash and runway, every block.
- Timing Deals visible before announcements.
How it fits your platform
-
01
Screen
Checked before entry
-
02
Hold
As encrypted Notes
-
03
Move
Nothing linkable onchain
-
04
Review
Through viewing keys
- USDC + USDT on Arbitrum
- Non-custodial
- Independently audited
- Fits existing monitoring
When a regulator asks
-
01
Request arrives
Through your usual channel
-
02
You set the scope
One payment or a history
-
03
You disclose
Selective disclosure or viewing key
-
04
Verified
Nothing goes public
Who sees what
Funds entering or leaving Curvy show one side onchain.
| who | Counterparties | Amounts | Balances |
|---|---|---|---|
| The public | Hidden | Hidden | Hidden |
| Your platform | Can see | Can see | Can see |
| Auditor or regulator | Only if you share your viewing key | Only if you share your viewing key | Only if you share your viewing key |
Compliance keeps working
-
Screening
Global Ledger checks before funds enter.
-
Claim-back
Rejected funds return to the sender.
-
Origin tracing
An encrypted origin record travels with funds.
-
Optional KYC
For deployments that need it.
Get the compliance one-pager
Controls, keys and disclosure on one page, for your compliance lead.
What compliance teams ask
- Licensing
- We make no licence claims. Built to fit your obligations.
- Regulator access
- Viewing keys and selective disclosure.
- Flagged funds
- Screened before entry. Rejected funds go back.
- What stays public
- One side of funds entering or leaving.
- Custody
- Non-custodial. Curvy can’t move or read funds.
- Monitoring
- Runs on the same data, through viewing keys.
Is it right for you?
Good fit if
- You hold or move business money in stablecoins
- Clients ask who can see their flows
- Your compliance team needs full records
- USDC and USDT cover your flows
Not yet if
- You need chains other than Arbitrum today
- You need fiat rails from this layer
- Payouts to outside wallets must hide the recipient
- You need licensing claims from a vendor
Questions
Does it weaken our compliance position?
It’s built not to. Funds are screened before entry, and your compliance team reads every payment through a viewing key. We make no claims about specific licences.
Can auditors or regulators see transactions?
Yes, when you give them access. A viewing key opens the history, and selective disclosure proves a single payment. Curvy never discloses.
What happens to flagged funds?
They don’t get in. Rejected deposits can be claimed back by the sender.
Is anything visible onchain?
At the edges. Funds entering or leaving Curvy show one side. Payments between Curvy balances show nothing linkable.