Spotlight
Embedded treasury: yield on idle platform balances
Platforms holding customer balances are increasingly asked to pay yield on them. The mechanics — and the regulatory questions — are less obvious than the pitch.
The problem
A platform that holds customer money — a marketplace between order and payout, a spend management product, a vertical SaaS with an embedded account — accumulates balances that sit idle. In a positive-rate environment, customers notice, and competitors start advertising a return.
What the approach looks like
Offering customers a yield on their platform balance, typically by routing idle funds into a money market fund, a treasury product or an interest-bearing arrangement with the underlying institution, and passing some or all of the return through.
Where it gets complicated
The pitch is simple; the classification is not. The moment a balance earns a return, questions arrive that did not apply to a payment balance:
- What is the product, legally? Interest on a safeguarded e-money balance, a deposit, and a holding in a fund are three different things with three different regulatory regimes and three different protections for the customer.
- Who is the product provider? If a fund is involved, someone is distributing it, and distribution of investment products is a regulated activity in its own right.
- What is disclosed? Customers must understand what they hold, what protects it, and that a return is not guaranteed. This is the area where enforcement attention concentrates.
- What happens to safeguarding? Funds that must be safeguarded cannot simply be redeployed. The arrangement has to be designed around that constraint, not despite it.
The stack
- Treasury & embedded investing — the yield product and its distribution.
- Banking-as-a-service — the underlying account and safeguarding arrangement.
- Core banking & ledger — accrual, allocation and per-customer reporting, which is real engineering.
- RegTech & compliance — disclosures, suitability where applicable, and reporting.
Questions to put to providers
- What is the legal wrapper, and who is the product provider and the distributor?
- Which customer protections apply, and how are they described to end customers?
- How does this interact with safeguarding on the underlying balances?
- How is yield accrued and allocated per customer, and what does the customer statement look like?
- What are the tax reporting obligations, in which jurisdictions, and who discharges them?
- What happens operationally on a redemption spike?
Honest assessment
The economics are attractive and the regulatory perimeter is the entire difficulty. This is not a feature to ship quickly; it is a product decision with a compliance workstream attached. Platforms that treat it as the latter succeed; platforms that treat it as a toggle on an existing balance tend to discover the problem after launch.
The treasury category is still onboarding providers on Finlane. You can publish an RFP in it, but expect fewer responses than in the established categories today.
- When this applies
- Meaningful customer balances sitting idle on the platform
- Build difficulty
- Medium
- Regulatory load
- High
Categories involved
Take this to providers
Describe the requirement once and let matching providers in each category respond. You stay anonymous until you accept one.
Related reading
- Seven reasons BaaS providers reject applicantsRejection from a banking-as-a-service provider is usually a risk decision made early and rarely explained. Here are the seven reasons it happens — and what to change before you apply again.
- Paying marketplace sellers across bordersSeller payouts across corridors: what breaks, which provider categories are involved, and the questions that separate a payout provider that works from one that looks like it does.
- Launching a business account inside a SaaS platformWhat a vertical SaaS platform needs to offer its customers a branded business account: the licence question, the stack, the onboarding reality and the sequence to procure in.