Key Concepts
| Term | Definition |
|---|---|
| Client | Your platform — the entity with a RebelFi account and API key |
| Recipient | A business customer of yours that needs ramp accounts |
| On-Ramp Account | A dedicated USD virtual bank account — payers send USD, it converts to USDC or USDT automatically |
| Off-Ramp Account | A crypto deposit address — send USDC/USDT to it, USD is delivered to a bank account |
| Transaction | A deposit (on-ramp) or payout (off-ramp) that has been converted and delivered |
| KYB | Know Your Business verification — required before a recipient can receive accounts |
| Payment Rail | The payment method used: ach, fedwire, or swift |
| Webhook | An event notification RebelFi sends to your configured endpoint |
Supported Chains
On-ramped USDC/USDT is delivered to your wallet on the chain of your choice:| Blockchain | Status |
|---|---|
| Polygon | Live |
| Arbitrum | Live |
| Base | Live |
| Ethereum | Live |
| Solana | Live |
How It Works
Create a Recipient
You create a recipient via the API. Optionally include a physical address (required for off-ramp).
KYB Approved
RebelFi sends a
customer.approved webhook. The recipient is now eligible for ramp accounts.Create Ramp Accounts
You create on-ramp and/or off-ramp accounts for the recipient via the API. Each account is bound to a specific wallet, asset, and payment rail.
Funds Flow
On-ramp: Payers send USD to the virtual bank account via ACH, wire, or SWIFT. USD converts to USDC/USDT automatically and is delivered to the designated wallet.Off-ramp: Send USDC/USDT to the deposit address. USD is delivered to the configured bank account.
In webhook events from the underlying payment infrastructure, recipients are referred to as “customers” (e.g.,
customer_id, customer.approved). This reflects the payment provider terminology.Next Steps
How It Works
Architecture, data flow, and fee model
Quick Start
Integrate in 5 steps
Authentication
API key setup
Webhooks
Event notifications