Architecture
RebelFi is the orchestration layer between your platform and banking infrastructure. You talk only to our API — we handle KYB, virtual bank account issuance, USD → USDC conversion, and delivery.Your Platform
Calls the RebelFi API to create merchants, query transactions, and receive webhook events
RebelFi
Orchestrates KYB, bank account issuance, conversion tracking, and event delivery
Banking Infrastructure
Handles virtual bank accounts, USD receipt, and USD → USDC conversion
Data Flow
When a payer sends USD to a merchant’s virtual bank account, the funds are automatically converted to USDC and delivered to your wallet.Fee Model
A percentage-based fee is deducted from each deposit before USDC delivery. The fee is expressed in basis points (bps). Example — $50,000 deposit at 25 bps total fee:| Amount | |
|---|---|
| USD deposited | $50,000.00 |
| Fee (25 bps) | $125.00 |
| USDC delivered | $49,875.00 |
Wallet Model
All on-ramped USDC from all merchants settles into a single wallet address that you designate during onboarding. You maintain per-merchant accounting via the transaction data we provide (each transaction is tagged with its merchant).Per-merchant wallet provisioning is available — contact us to enable.
Merchant Lifecycle
- You create a merchant via
POST /v1/ramp/merchants - RebelFi returns a hosted KYB URL
- The merchant completes the KYB form
- On approval, a virtual bank account is automatically issued
- RebelFi sends a
customer.approvedwebhook with bank account details
Transaction Lifecycle
Once a merchant has an active bank account, incoming USD deposits flow through these states:| Status | Meaning |
|---|---|
pending | Deposit detected, conversion not yet started |
processing | Conversion in progress |
completed | USDC delivered to your wallet |
failed | Conversion failed — review required |
reversed | Deposit was reversed — funds returned to sender |