Onramper Accounts are a separate product from the Transfer API. They use different endpoints and do not support bank account creation via the Transfer API.
Endpoint
Authentication
All requests require a Bearer token in theAuthorization header.
Request parameters
The ID of the customer who will own this Onramper Account.
The fiat currency the virtual account accepts for deposits. Must be
"usd" or "eur".The stablecoin that deposited fiat is converted into. Must be one of
"usdc", "usdt", or "eurc". Must be compatible with the chosen network.The blockchain network the destination wallet is on. Must be one of
"arbitrum", "avalanche", "base", "ethereum", "polygon", "sol", or "tron". Must support the chosen destinationCurrency.The on-chain wallet address where converted stablecoins are delivered. Must be a valid address format for the specified
network.Optional integrator fee in basis points (1 bps = 0.01%). Defaults to
"0" if not provided. This fee is added on top of the SpherePay platform fee.Response fields
Unique identifier for the Onramper Account.
ID of the customer who owns this account.
Whether the account is currently accepting deposits.
Bank account details your customer uses to deposit fiat funds.
The crypto destination where converted funds are sent.
Fee breakdown applied to each deposit conversion.
ISO 8601 timestamp of when the account was created.
ISO 8601 timestamp of the most recent update.
Error responses
| Status | Code | Description |
|---|---|---|
400 | address/invalid | One or more request parameters are invalid. |
404 | resource/not-found | The specified customer ID does not exist. |
422 | validation/failed | Validation failed. The response includes a per-field errors array. |