With RebelFi
- Float earns yield during defined windows
- Liquidity buffers are enforced by policy
- Ring-fencing isolates treasury strategies from customer flows
- Automatic unwind logic is built into the flow state machine
Use case
Earn yield on operational float—escrow windows, settlement buffers, payout queues—without breaking liquidity, reversibility, or compliance.
Stablecoin businesses hold capital in motion states: waiting for settlement cutoffs, reconciliation, compliance checks, chargeback-like windows, and payout batching. That capital is idle by default—not because yield is hard, but because operations needs guarantees: liquidity on demand, clean provenance, and predictable unwind behavior.
Escrow, settlement buffer, payout queue, or prefunding.
Minimum buffer, max deploy %, cooldowns, approved venues.
Only institution-owned, provenance-clean funds touch yield strategies.
At cutoff or trigger, funds return to operational wallet before payouts/settlement.
Full state transitions and wallet provenance are exportable.
You hold USDC for 6–48 hours between inbound receipts and outbound settlement. RebelFi deploys eligible treasury float during the window and unwinds automatically before scheduled settlement.
You hold funds for dispute windows (24–14 days). RebelFi encodes the hold logic and yields on the hold balance until release conditions are met.
If you prefund corridors, RebelFi helps net and optimize the float posture and makes the remaining buffer productive.
Min %, min amount
Per wallet
DeFi + regulated
Per transition
Toggles
Deploy only during X hours
No. Zero-custody execution.
No—modular sources. You choose your risk profile.
Yes.
Provider disable + unwind path triggers automatically.
Let's analyze your operational windows and show you what yield looks like when it's embedded into your flows.