At a glance
- What changed
- Aave and Privy announced an integration that lets apps built on Privy offer access to Aave-powered yield.
- Who it affects
- Fintechs, neobanks and other businesses building products with Privy, and users of apps that choose to enable the feature.
- When
- Aave published the announcement on 6 October 2026. The initial self-serve configuration is Aave USDC on Base; no consumer rollout timetable is stated.
Aave App partner offer and conditions ↓
A new integration for apps, not an automatic wallet bonus
Aave and Privy announced a connection between Aave lending markets and Privy Earn, a product that businesses can use to add financial features to apps built with Privy’s embedded-wallet tools. The first self-serve configuration is a vault that supplies USDC to Aave on Base. That gives fintechs, neobanks and other Privy customers a way to offer an Aave deposit flow inside their own products.
The announcement is aimed at software builders. It does not say that every existing Privy wallet will start earning interest, or that Privy is launching a consumer savings account. A business has to set up the vault, connect its app to the relevant API and decide whether to expose the feature. The user experience, disclosures and any regional restrictions will therefore depend partly on the app offering it.
What happens to a deposit
Aave is a lending protocol: suppliers place supported assets into a market, where borrowers can use available funds under the protocol’s rules. In return, a supplier receives an aToken, a blockchain record that represents the supplied position. Interest is not a fixed coupon. The rate changes as the relationship between supplied and borrowed funds changes, so an advertised or observed annual percentage yield is a snapshot rather than a promise.
Privy’s actions API is designed to prepare and submit the wallet operations an app needs for deposits and withdrawals, while helping the app track a user’s vault position. The documented deposit flow can bundle the required token approval with the deposit call. The app still needs the user’s supported wallet, the correct token and chain, enough balance for the transaction, and an onchain confirmation before it can show the deposit as complete.
Builders choose the vault and the app’s share
The setup process begins in Privy’s dashboard, where a developer creates or selects an Aave vault, configures an app fee and assigns an administrative wallet. The app then uses the vault identifier with Privy’s API when it requests a deposit, position or withdrawal. The fee is a share of yield, not a percentage added to the user’s deposit amount.
Privy’s Aave documentation permits a developer-configured fee from zero to 100 percent of yield. The user receives the remaining yield after that app share, if any. A fee can accrue to the app’s administrative wallet and may need to be collected separately. A screen that shows only the protocol’s gross rate can therefore overstate what the end user receives; apps need to make their own fee treatment clear.
Yield data needs context
Privy documents API fields for a vault’s annualized yield, total value locked and available liquidity, along with separate user and app yield figures. These are useful operational readings, but they answer different questions. Total value locked describes the scale of deposits, while available liquidity helps indicate what can presently be withdrawn. Neither metric guarantees a future rate or a same-day exit.
Aave’s supply rate moves with market use. When borrowers take a larger share of available funds, the protocol’s rates can change; when funds are repaid or demand falls, they can change again. The dashboard value is not the same as a bank savings rate that an institution promises to maintain. An app should date its figures, explain whether they are gross or net of its own fee, and avoid turning a current estimate into an expected payout.
A withdrawal is an onchain request, not a guaranteed instant transfer
The Privy withdrawal endpoint lets an app request some or all of the user’s position back into the supported asset. Its documentation tells builders to check the vault’s available liquidity before a large withdrawal. In Aave, supplied assets may be borrowed, so the amount immediately available can be lower than the total supplied. A request can fail or be delayed by the state of the market, the wallet action or the chain.
A successful withdrawal also requires a transaction to be signed and confirmed. Privy provides wallet and API infrastructure for that workflow; it does not remove Aave’s market conditions. Any gas sponsorship depends on the integrating app’s configuration. Users should see a clear pending state while an operation is awaiting confirmation, rather than an interface that treats a submitted request as settled cash.
The integration leaves protocol and app risks in place
Privy is the wallet and developer infrastructure in this arrangement; Aave is the external protocol receiving the supplied asset. A user is not simply moving money into a conventional deposit account. The app must explain that a third-party protocol is involved and let the user deliberately direct funds into the vault. The app also chooses the product configuration, including the vault and any yield share it keeps.
Aave’s own risk documentation discusses smart-contract, oracle, collateral and network risks. A software flaw, an inaccurate price feed, stressed borrowing conditions or a chain problem can affect a position even when the app’s wallet works as designed. The integration does not make those risks disappear, insure a balance or promise a positive return. Privy’s guides also state that app integrations must present the yield source and the user’s action clearly.
What the launch changes for customers
For an app provider, Privy Earn reduces the amount of custom wallet plumbing needed to offer a yield feature connected to Aave. The initial self-serve route is narrow: USDC, Base and an Aave vault. Privy says builders seeking other supported assets or chains should contact its team, so the announcement is not evidence that every combination is already available through self-service.
For an end user, the practical question is whether a particular app has actually enabled the feature and how it presents the net rate, the app’s fee, withdrawal liquidity and protocol risks. Until an app launches the option, a general Privy wallet does not acquire this feature by default. When it does appear, the displayed terms and transaction preview—not the integration headline—will explain what that app is offering.
6% variable APY on USDC
Current variable base APY on eligible balances up to $100,000; the portion above earns 4.5%. Rates are not guaranteed. Access and referral boosts depend on your country and account. Check the current rate in the app.
Conditions
The code and partner link have no expiry. Campaign dates, benefits and eligibility are separate and may change. Check the provider’s current terms before signing up.
We may earn a commission, at no extra cost to you.