Transfers Overview
What transfers are in SpherePay, the two transfer directions, and how to choose your integration path.
A transfer in SpherePay is the movement of funds between a crypto wallet and a bank account. Every transfer has a source and a destination — one crypto (wallet), one fiat (bank account).
Transfer Directions
SpherePay supports two directions. The direction is determined by what you set as source and destination on the transfer request — the API endpoint is the same for both.
| On-Ramp | Off-Ramp | |
|---|---|---|
| Source | Bank account (fiat) | Wallet (crypto) |
| Destination | Wallet (crypto) | Bank account (fiat) |
| Flow | Fiat → Stablecoin | Stablecoin → Fiat |
| Customer sends | USD, EUR | USDC, USDT, EURC |
| Customer receives | USDC, USDT | USD, EUR |
Prerequisites
Before a transfer can be created, the customer must have:
- An approved identity — the customer's verification profile must be
approved. See Customers & Onboarding. - A registered bank account — for the fiat side of the transfer. See Bank Accounts.
- A registered wallet — for the crypto side of the transfer. See Wallets.
Integration Paths
SpherePay provides two ways to move funds. Start with the Transfer API — it covers both directions and gives you full control. The automated products are add-ons to consider once the core flow is working.
| Transfer API | Automated Transfers | |
|---|---|---|
| How it works | You create each transfer explicitly. SpherePay returns unique deposit instructions (account + memo) per request — the customer sends funds to those instructions and SpherePay matches the memo to process it | A dedicated account or address is created once per customer. Any funds sent to it are automatically converted and forwarded — no per-transfer action required |
| Control | Full — you initiate and attribute each transfer individually | Hands-off — conversion triggers on deposit; no per-transfer tracking |
| Best for | On-demand transfers where you need control over timing, amount, and attribution | Customers who frequently on-ramp or off-ramp to the same address — create one account per customer |
| Products | Transfer API | Onramper Accounts (fiat → crypto), Offloader Wallets (crypto → fiat) |
Automated Transfers are not multi-tenant
Onramper Accounts and Offloader Wallets have no per-transfer attribution. Without a unique memo or deposit address per customer, identifying which customer sent a given deposit requires polling the transfer list and manually matching by amount, timing, or source — which is error-prone and has no webhook support. Always create one account or wallet per customer.
Start with the Transfer API
For most integrations, the Transfer API is the right starting point. Onramper Accounts and Offloader Wallets are purpose-built add-ons — consider them once the core transfer flow is working.
Last updated on