You already hold USDC. Put it to work.
Yield on the idle portion of your stablecoin treasury, with coverage you do not have today.
Rate grid as of September 2026 · USD or USDC · KYB required before the first deposit
The short version
- Your treasury already holds USDC, so onboarding is a KYB and a transfer — no bank to convince, no on-ramp to approve.
- Split the balance before picking a tier: operating float stays where it is, the buffer goes on the no-lock tier, the idle reserve takes a term.
- 6.00% APY with no lock, 6.25% to 6.75% on a 3 to 12-month term, 7.00% introductory for the first six months — as of September 2026.
- Eligible funds are covered through OpenCover for up to 100% of their USD value, subject to policy terms. A stablecoin depeg is not covered, and this is not FDIC insurance.
- You keep your multisig, your signers and your signing policy. Only the allocated slice moves, and it comes back within 48 hours to a destination fixed at KYB.
Conversion is not your problem.
Most of what a corporate treasury has to work through before touching this product — approving a stablecoin, agreeing an accounting line, getting comfortable with an on-chain balance — you settled a long time ago. What is left is a narrower question: what happens to the part of that balance that never moves.
Already solved on your side
Still open
What this changes about onboarding
A company funding in USD spends most of its onboarding on the parts around the product: convincing a bank, agreeing a transfer route, explaining a stablecoin to a board that has never held one. You skip all of it. Funding is a transfer from a balance you already control, and the only gate left is the KYB — which for a web3 entity has its own shape, covered further down this page.
Yield on the portion that never moves.
The whole exercise is deciding which slice of the stablecoin balance is genuinely idle. Split it three ways first, then pick a tier for each — not the other way round.
Operating float
Payroll, vendors, gas, market-making float, anything with a date on it. This is not the portion we are talking about.
Buffer
Money you will probably need this year, on a date nobody can name yet. The cost of guessing wrong has to be zero.
Idle reserve
Raise proceeds, accumulated protocol revenue, the slice of treasury already diversified into stablecoins and left alone.
The rate grid, and where each tier fits
| Term | APY | Where it fits |
|---|---|---|
| Introductory rate | 7.00% | First 6 months |
| No lock | 6.00% | Buffer you may need on short notice |
| 3-month lock | 6.25% | Cash earmarked for a quarter-end outflow |
| 6-month lock | 6.40% | A reserve slice with a horizon you can defend |
| 9-month lock | 6.60% | Runway you have already committed not to touch |
| 12-month lock | 6.75% | The portion that has not moved in a year |
On a locked tier, an early exit returns the capital and forfeits the accrued interest. There is no penalty on the principal. Withdrawals are available within 48 hours on every tier.
Illustration on the no-lock tier, against a balance that currently earns nothing where it sits, before tax, assuming the rate holds for a full year. The rate is not guaranteed. If part of your balance is already deployed somewhere, that position is your benchmark, not zero — run your own numbers.
Why not run it in-house.
You can open the same positions on the same protocols yourself, and your team probably knows how. The deposit is the easy part. What follows it is a standing operational commitment — here is the honest list of what you take on.
What you take on, item by item
Pool composition drifts. Emissions get cut. An oracle gets re-pointed. A governance proposal that changes a risk parameter lands on a Friday night with a 48-hour voting window. Watching a position is not a weekly task on someone’s board — it is an on-call rotation, and someone on your team has to own it alongside the job they already have.
Protocol cover exists, and you can buy it yourself. You then own the renewal calendar, the per-protocol limits, and the exclusion list you have to read before you assume a loss is covered. Skipping that step is a decision too: the entity underwrites the failure on its own balance sheet.
In-house positions are usually built by an engineer, not by the finance team. The knowledge of why this pool, why this cap, why this exit trigger, lives with them. When they leave, the position outlives the reasoning — and the signer set has to be reorganised around a live allocation.
The number on the analytics page is gross. Entering, claiming rewards, swapping them back to USDC and exiting all cost gas and slippage, and the exit costs most when you least want to pay it. What you model in a spreadsheet and what you realise over a year are two different numbers.
Position-level history, valuations at period end, and an explanation of where the yield came from that does not require reading a block explorer. Building that record after the fact is slower than producing it as you go.
When in-house is the right call
If two or more of those describe you, we are an intermediary between you and something you already do well. Keep doing it.
The coverage you do not have today.
USDC sitting in your own wallet has no protocol cover, and neither does a position you opened yourself unless you bought cover for it. Eligible funds here are covered through OpenCover for up to 100% of their USD value, subject to policy terms, limits and exclusions.
Covered
via OpenCoverNot covered
This is not FDIC insurance, and nothing here makes it one. A depeg of the underlying stablecoin — the risk your treasury already carries by holding USDC — stays outside the policy.
Selected protocols
Our selection criteria
Curve 
Pendle 
Balancer 
Aave Names your team already knows, which is the point: the difference is not the venue, it is who watches it and what happens when the code fails. The coverage and risk page sets out the exact scope, the limits and the exclusions.
KYB for web3 entities.
KYB is required before the first deposit, and a foundation, a DAO wrapper or a two-jurisdiction group raises questions a single operating company does not. None of them are blockers. They are just easier to answer before you start than halfway through.
The five questions a web3 file raises
Crypto-native groups rarely have one company. A foundation holds the protocol, an operating company employs the team, and a wrapper sits around the DAO. The entity that deposits is the entity we contract with and screen, so settle that before you gather a single document — the answer is usually whichever entity already holds the balance on its balance sheet.
Token holders are not beneficial owners in the KYB sense, and a token distribution is not an ownership chain. What we need is the directors, managers or council members, the people who can act for the entity, and identification for each signatory.
A board, member or council resolution authorising the account. Holding a key in a multisig is not, on its own, evidence that a person can commit the entity — the two are separate questions and both get asked.
Token sale proceeds, accumulated protocol revenue, an investment round, a diversified slice of a native token position. A short written explanation, with the addresses that back it. On-chain history is easier to evidence than a bank ledger, and it is treated the same way.
The funding address and the withdrawal destination are named during KYB and confirmed once. That is what makes a 48-hour withdrawal window possible — there is no destination to verify at the moment you ask for the money.
What we will not tell you from a web page
Whether your jurisdiction of registration is eligible. We do not publish that list, because it moves with sanctions regimes and guidance, and a stale page would send a finance team down the wrong path. The determination is made against the list in force on the day we review your file, and you get the answer in writing before you commit anything. If your structure is unusual, ask first — it is one message and it saves you assembling a file you may not need.
It sits alongside your custody, not instead of it.
You keep your multisig, your custodian and your signer set. What changes is the control model for the allocated slice, and only for that slice. Here is where the funds sit at each stage.
Stage by stage
Before deposit
Your wallet, your multisig or your custodian. You, on your own signing policy.
Funding transfer
Moving to the address issued at onboarding. You sign it — Coinstancy never becomes a signer on your wallet.
Deployed
Non-custodial DeFi protocols selected and monitored by Coinstancy. Coinstancy manages the allocation. You hold no keys to the position.
Withdrawal requested
Being unwound from the protocols. Coinstancy, within the 48-hour window.
After withdrawal
Back at the destination named during KYB. You again.
What stays with you
What you give up on the allocated slice
A reasonable first allocation
Take the slice of USDC that has not moved in two quarters, put it on the no-lock tier, and leave the operating float exactly where it is. That gives your team a full withdrawal cycle to test — request, 48 hours, funds back at the address you named — before anything is committed to a term. If the cycle behaves the way this page says it does, extend the term. If it does not, you have lost nothing but a few days of accrual.
Request access, or ask the hard questions first.
Open an account directly. If your finance team needs the coverage terms and the KYB requirements before that, a call is the faster route.