Each Onramper Account should belong to a single customer. If multiple customers share a virtual account, matching deposits to customers requires manually correlating by amount and timing — which is error-prone. Always create one Onramper Account per customer.
Endpoint
Authentication
All requests require a Bearer token in theAuthorization header.
Path parameters
The Onramper Account ID whose transfers you want to list (e.g.,
"virtualAccount_a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6").Response fields
The response is an array of transfer objects. Each object represents one fiat-to-crypto conversion processed through the account.Unique identifier for the transfer.
Current status of the transfer (e.g.,
"completed", "pending", "failed").The fiat amount received, as a string decimal.
The fiat currency of the deposit (e.g.,
"usd").The stablecoin amount delivered after conversion and fees.
The stablecoin the deposit was converted into (e.g.,
"usdc").The blockchain network the stablecoins were delivered on.
The on-chain wallet address that received the converted funds.
ISO 8601 timestamp of when the transfer was initiated.
ISO 8601 timestamp of the most recent status update.
Error responses
| Status | Code | Description |
|---|---|---|
400 | address/invalid | The request is malformed or the ID format is invalid. |
404 | resource/not-found | No Onramper Account with the specified ID exists. |
422 | validation/failed | Validation failed. The response includes a per-field errors array. |