How Neobanks Earn Yield on Customer Float with Stablecoins

Neobanks hold significant customer deposits. Most earn almost nothing on them.

The gap is structural. Traditional sweep infrastructure moves money overnight — far too slow to capture yield on balances that cycle through the platform in hours. Stablecoin architecture closes that gap by attaching yield logic directly to the balance, not to the account it rests in. The result: customer float that earns continuously, from the moment it arrives until the moment it leaves, regardless of how fast it moves.

This post covers the specific mechanics — how neobanks classify deposits for yield purposes, how sweep architecture routes funds to vaults, how yield is distributed between the neobank's P&L and customers, and where the regulatory constraints sit.

How neobanks classify deposits before deploying yield

Not all customer deposits are treated the same in a yield architecture. The first decision is classification.

Demand deposits

Demand deposits are available to the customer at any moment without notice. Checking accounts, current accounts, and standard digital wallet balances all fall into this category. A customer can initiate a payment or withdrawal at any point, which means yield deployment against demand deposits must preserve full instant-access liquidity.

For stablecoin yield purposes, demand deposits go into instant-access vault positions only — yield venues that can redeem within 30-60 seconds with no withdrawal penalty. Tokenized short-duration T-bill funds with real-time redemption capacity are the primary vehicle. Yield rates are lower than term positions, but the liquidity constraint is non-negotiable. A missed settlement window because funds are locked in a term vault is a worse outcome than lower APY.

The aggregate size of the demand deposit pool is more predictable than any individual balance, which is the insight that makes deployment viable. If 40,000 customers each hold a balance that individually fluctuates, the aggregate pool fluctuates very little. Stablecoin yield architecture deploys against the aggregate pool, maintaining a liquidity buffer sized to peak expected outflows.

Term and locked deposits

Some neobanks offer fixed-term savings products — 30-day, 90-day, or longer locked balances that the customer commits not to access until maturity. These are structurally different from demand deposits because the withdrawal timing is known in advance.

Against locked deposits, neobanks can deploy into higher-yielding, lower-liquidity positions. On-chain lending protocols with 7-day withdrawal windows, tokenized bond funds, or stablecoin issuer reward programs with minimum lockup periods all become accessible. Yield on term deposits can run 150-300 basis points above the demand deposit rate for the same stablecoin, reflecting the value of predictable liquidity to the vault counterparty.

The classification sits at the ledger level. Each deposit record carries a liquidity type tag — demand or term, with maturity date for term — that the yield routing layer reads before selecting a vault. No manual intervention required.

Sweep architecture: how funds move from customer account to yield vault

The sweep process in stablecoin operations has three stages: aggregation, screening, and deployment. This is where [stablecoin operations](/blog/stablecoin-operations-neobanks) differs most sharply from traditional overnight sweep accounts.

Stage 1 — Aggregation

Incoming customer deposits are ingested and converted to a stablecoin representation at the platform level. The neobank maintains a stablecoin treasury (USDC, EURC, or a regulated e-money token) that backs customer balances. The user-facing experience is unchanged — customers see their fiat balance as always. Underneath, the balance is now programmable and can carry yield instructions.

The aggregation layer pools demand-classified balances into a common yield pool. Individual customer balances are tracked at the ledger level; the yield pool itself operates as a single deployable unit. This is the mechanism that makes per-second yield accrual on small balances economically viable — you are not deploying 40,000 individual £200 positions, you are deploying one £8 million pool.

Stage 2 — KYT screening and ring-fencing

Before any funds reach a yield vault, they pass through Know Your Transaction (KYT) screening. Funds with verified provenance enter the yield-eligible pool. Funds that trigger risk flags are quarantined and excluded from yield deployment until reviewed.

This is the compliance gate that makes the entire architecture defensible. The [ring-fencing layer](/blog/ring-fencing-stablecoin-compliance) maintains strict separation: client funds in the yield pool are segregated from the neobank's own operational capital. Yield attributions flow back through this separation so the accounting treatment — which yield belongs to the neobank's P&L, which belongs to the customer pool — is tracked automatically, not reconstructed at audit time.

Stage 3 — Vault selection and deployment

Clean, ring-fenced funds are deployed to yield venues according to treasury policy rules:

• Demand deposits → instant-access tokenized T-bill funds (Ondo OUSG, BlackRock BUIDL equivalents with real-time redemption) or stablecoin issuer reward programs

• Term deposits → higher-yield venues matched to maturity profile — structured lending protocols, longer-duration bond funds

• Operational float → same instant-access layer as demand deposits, sized at peak outflow buffer

The vault selection is rules-based and automated. The neobank defines policy — maximum allocation per venue, minimum liquidity ratio, acceptable counterparty risk tiers — and the infrastructure routes accordingly. No DeFi expertise required internally.

When settlement is needed, funds withdraw from the vault within 30-60 seconds and become available for payment processing. Yield accrued during the vault period is captured and attributed to the correct pool.

Revenue model: yield at scale

The core question for any neobank evaluating this architecture is: what does it actually generate?

The table below models gross yield revenue across three deposit scale points, with three yield efficiency scenarios. Conservative reflects deployment into instant-access T-bill positions only, limited vault diversification. Moderate reflects demand-demand split with some term product, two to three vault types. Optimized reflects full demand/term classification, multi-vault routing, and stablecoin issuer reward programs layered on top.

All scenarios use a blended APY range based on current institutional stablecoin yield market conditions. Rates will vary.

*Revenue figures are gross yield before vault fees, infrastructure costs, and any yield sharing with customers. Yield rates are illustrative based on market conditions as of early 2026 and will vary. Past performance does not guarantee future results.*

For a neobank at $250M in average deployable float, the difference between conservative and optimized deployment is $7.5M in annual gross revenue. The gap between having no yield architecture at all and conservative deployment is $8.75M. These are not marginal improvements — they are margin-transforming for a neobank under profitability pressure.

The optimized scenario requires full demand/term classification, multi-vault policy, and stablecoin issuer reward program enrollment. It is achievable in production, but it takes longer to implement and requires more regulatory groundwork in most jurisdictions.

Yield distribution: neobank P&L vs. customer pass-through

Once the yield is earned, the neobank must decide how to distribute it. This is simultaneously a regulatory question and a competitive one.

Decision tree: when to keep yield vs. pass to customers

The decision turns on three factors: regulatory classification, product positioning, and competitive response.

Regulatory classification — the gating factor

Most neobanks operating under EU payment institution licenses, UK FCA EMI authorizations, or US MSB frameworks are not licensed to pay interest to retail customers. Paying yield directly on customer deposits — framed as interest — triggers banking license requirements they do not hold.

The structural workaround differs by jurisdiction. In the EU, yield can be returned to customers as a cashback or fee reduction program, not as interest, if the legal structure is designed correctly. In the UK, structuring yield as a customer reward rather than a deposit return avoids deposit-taking characterization under the FSM Act. In the US, the GENIUS Act (Pub. L. 119-27) establishes a framework for stablecoin payment instruments that is not equivalent to a deposit — yield programs structured around stablecoin balances rather than traditional deposit accounts occupy different regulatory territory, though specific advice is required.

Competitive positioning — the strategic factor

If the neobank retains all yield internally, the P&L benefit is maximized. The risk: competitors offering yield-sharing will attract rate-sensitive customers, particularly in the higher-balance segments where yield math is most visible to users.

If the neobank shares yield partially (e.g., passes 50% to customers), they gain a differentiated product — a "savings" feature that doesn't require a banking license if structured correctly — while retaining meaningful gross margin. This is the position most neobanks in the EU are moving toward under MiCA's developing yield-sharing guidance.

The simplified decision logic:

The [MiCA-compliant stablecoin yield](/blog/mica-compliant-stablecoin-yield) post covers the EU-specific regulatory mechanics in detail.

Yield retained on operational float — no licensing question

Regardless of the customer pass-through decision, neobanks can capture yield on their own operational float without any retail yield distribution questions arising. The neobank's own capital — fee revenue, transaction income, equity — is not customer money and does not trigger customer yield distribution requirements.

For most neobanks, operational float represents 5-10% of total platform float. At $1B in customer deposits, operational float might be $50-100M. At 5% APY, that is $2.5-5M in yield that sits entirely in the neobank's P&L with no regulatory complexity. This is the unambiguous starting point — capture operational float yield first, then build toward customer float deployment.

Regulatory constraints: what limits yield deployment

The regulatory frame varies by jurisdiction, but three constraints are universal.

Safeguarding / ring-fencing requirements: Customer funds must remain segregated from the neobank's own capital. The yield deployment architecture must track customer funds through vault positions and back to the customer pool — not blend them into a unified pool. Under MiCA Article 68, this is a hard architectural requirement for EU-facing operations. The GENIUS Act establishes equivalent segregation obligations for US stablecoin payment instruments.

Reserve backing and asset quality: Yield venues must maintain adequate liquidity. MiCA requires that customer assets be held in low-risk, highly liquid instruments. This limits the yield venue universe to tokenized government securities, regulated money market equivalents, and stablecoin issuer programs with verifiable reserve backing. High-risk DeFi protocols that may offer higher APY are not compliant deployment venues for customer float.

Disclosure requirements: Customer agreements must clearly disclose how float is deployed, what yield is generated, and how it is allocated. Neobanks that earn yield on customer float without disclosing the arrangement face regulatory exposure regardless of whether yield is passed to customers or retained. The disclosure framework should be built before deployment, not retrofitted.

For the mechanics of clean fund separation under these constraints, see the [ring-fencing stablecoin compliance](/blog/ring-fencing-stablecoin-compliance) architecture post.

FAQ

Can a neobank earn yield on customer stablecoin deposits without a banking license?

The answer depends entirely on jurisdiction and the specific yield-generation mechanism. In the US, earning yield on customer deposits generally triggers either banking license requirements (under state money transmitter or federal banking charters) or securities registration obligations under the Howey test. Neobanks operating under state money transmitter licenses can hold customer stablecoins but cannot directly lend or invest those funds for yield without additional licensing. The workaround used by several fintech platforms involves partnering with a licensed bank that holds the deposits and shares a portion of the yield through a revenue-sharing agreement. In the EU, the MiCA framework allows crypto-asset service providers (CASPs) to custody stablecoins and potentially earn yield through authorized investment activities, but Article 67 prohibits paying interest on e-money tokens to retail holders. Singapore's Payment Services Act permits major payment institutions to earn yield on customer float through approved low-risk investments. The regulatory path typically costs $200K–$500K in legal and compliance setup depending on jurisdiction.

What is the difference between demand deposit yield and term deposit yield for neobanks?

Demand deposit yield comes from investing customer balances that can be withdrawn at any time, while term deposit yield comes from funds locked for a specified period. The distinction creates fundamentally different risk and return profiles for the neobank. Demand deposits require instant liquidity, limiting investment options to overnight lending, liquid money market instruments, and short-duration DeFi protocols with instant withdrawal capability. Current demand deposit yield on stablecoin platforms ranges from 3.5–5.5% APY. The neobank typically retains 60–80% of this yield as revenue and passes 20–40% to the depositor. Term deposits unlock higher-yield strategies including fixed-rate lending protocols, structured DeFi vaults with 7–90 day lockups, and real-world asset (RWA) protocols. Term deposit yields run 6–12% depending on duration and protocol risk. The neobank captures a larger spread because the predictable lockup period enables more efficient capital deployment. At $50M in total deposits, the revenue difference between a pure demand model (earning $1.2M–$1.8M annually) and a blended 70/30 demand-term model (earning $1.8M–$2.6M) can reach $600K–$800K per year.

How do neobanks avoid regulatory problems when earning yield on customer float?

Regulatory compliance for neobank float yield requires navigating 4 distinct legal frameworks, varying significantly by jurisdiction. First, the neobank must ensure its custody arrangement qualifies as safeguarding rather than deposit-taking. In the UK, this means compliance with FCA Client Money (CASS) rules requiring segregation of customer funds from operational capital. In the US, state money transmitter licenses impose permissible investment restrictions that typically limit float deployment to government securities and FDIC-insured deposits. Second, yield-generation activities must not transform the product into a security under applicable securities law. The SEC has taken enforcement action against platforms offering yield on crypto deposits without registration, citing Howey test violations. Third, the neobank must maintain adequate liquidity reserves, typically 100% of demand deposit liabilities in liquid assets redeemable within 24 hours. Fourth, disclosure obligations require clear communication to customers about how funds are invested and what risks apply. Most compliant neobanks operate through a bank partnership model placing the licensed entity between the customer and yield strategy.

At what deposit scale does stablecoin float yield become material for a neobank?

Stablecoin float yield becomes operationally material at $10M–$15M in average daily deposits, but strategic materiality requires $50M or more. At $10M in deposits earning a blended 5.5% yield with 65% revenue retention, the neobank generates roughly $357K annually from float. This covers 1–2 full-time engineering salaries for treasury infrastructure maintenance but does not meaningfully impact unit economics. At $25M, annual float revenue reaches $890K, which begins to offset customer acquisition costs (typically $25–$75 per user for fintech neobanks) for 12K–36K new customers. At $50M, the $1.78M annual yield revenue starts changing the business model fundamentally, enabling the neobank to offer fee-free accounts subsidized by float income. The inflection point where float yield becomes the primary revenue driver rather than a supplement typically occurs at $100M–$200M in deposits, generating $3.5M–$7.0M annually. At this scale, the neobank can invest in dedicated treasury management infrastructure, hire specialized DeFi strategists, and negotiate institutional-tier access to yield protocols with 50–150 basis point advantages over retail rates.

*This post is for informational purposes only and does not constitute legal or financial advice. Yield rates are illustrative based on market conditions as of early 2026 and will vary. Regulatory requirements differ by jurisdiction. Past performance does not guarantee future results. Consult qualified legal and financial counsel before implementing any stablecoin yield strategy.*

The math favors moving early

Float yield is a margin lever that requires no new customers and no new products. The capital is already in the platform. The architecture — sweep classification, KYT-gated ring-fencing, vault routing, attribution — is the implementation cost. Neobanks that build it internally spend 12-18 months before earning the first basis point. Neobanks that treat stablecoin operations as a platform dependency are in production inside six months.

For context on how [money-in-motion and money-at-rest](/blog/money-in-motion-vs-money-at-rest) differ in yield potential, and how an operations layer captures yield across both states, start there. For the regulatory mechanics of clean fund separation under MiCA and the GENIUS Act, see [ring-fencing for stablecoin compliance](/blog/ring-fencing-stablecoin-compliance).

Ready to model your float opportunity? [Request a yield assessment](/contact) and we will map your deployable float pool, model revenue across conservative to optimized scenarios, and outline the compliance architecture for your regulatory environment.

About RebelFi

RebelFi builds the operations layer for stablecoin-native businesses. The platform provides yield-in-transit, ring-fencing, and Secure Transfers — infrastructure that lets fintech treasuries earn on float, stay compliant, and move money safely. Learn more at [rebelfi.com](https://rebelfi.com).