Use case

Yield for Customers (without custody risk)

Offer customer-facing yield while keeping segregation, clean provenance, and operational control.

Customer yield is easy. Customer yield that's compliant is not.

Most "yield" products either (1) commingle customer funds with treasury, (2) push users into DeFi exposure directly, or (3) create audit nightmares when funds need to move back to payout/withdrawal rails.

With RebelFi

  • Customer balances remain segregated by design
  • Treasury strategies remain ring-fenced
  • Yield accrual can be attributed without exposing strategy wallets to customers
  • Withdrawals route through clean rooms to preserve provenance

Without RebelFi

  • Customer funds commingle with treasury
  • Direct DeFi exposure creates regulatory risk
  • Withdrawal provenance is unclear
  • Audit trails are incomplete

Two deployment models

  1. 1

    Model A: Vault-backed customer accounts (high segregation)

    One vault per customer or per program segment. Yield routing policy scoped per vault. Best when: strict segregation or per-customer constraints.

  2. 2

    Model B: Pooled sub-ledger accounts (high velocity)

    Shared strategy wallet with internal attribution ledger. Best when: many users, high TX velocity, cost sensitivity.

  3. 3

    Choose your model

    Work with our team to select the right architecture for your compliance and operational requirements.

Customer balances (L1/L2) never touch DeFi

Customer balances never touch DeFiCustomer Operations LayerDeposits, Withdrawals, BalancesSEGREGATION BOUNDARYTreasury / Yield LayerInstitution-Owned Capital OnlyQuarantine Layer123

Example workflows

Wallet product offering "Earn on idle USDC"

Customers see yield accruing on their balances while you maintain full control over strategy allocation and risk management.

Exchange "customer yield" program

Offer competitive yield to customers with strict withdrawal hygiene and clean provenance routing.

Neobank-like stablecoin account yields

Instant withdrawals backed by buffered liquidity, with yield distributed to customer accounts automatically.

Policy knobs

Yield distribution

Customer vs platform share

Eligibility rules

Jurisdiction, tier, wallet type

Withdrawal liquidity targets

Buffer requirements

KYT gating thresholds

Quarantine rules

Frequently asked questions

Are customer funds used in DeFi?

Ring-fencing means only allowed structures touch yield. Customer ops never directly touch DeFi. Architecture prevents contamination.

How is yield attributed to customers?

Internal attribution ledger tracks yield per customer or segment, without exposing strategy wallet details.

What about regulatory compliance?

Segregation and clean provenance are built in. Work with your legal team on the specific regulatory framework.

Launch customer yield without rebuilding your compliance stack

Let's design a customer yield architecture that works with your existing compliance requirements.