Overview
Wallets are destination blockchain addresses where cryptocurrency is sent during on-ramp transactions. Each wallet is tied to a virtual machine (VM) type that determines which blockchains are compatible with that address. You can save wallets ahead of time or pass the address directly when creating a transaction.VM Types
ThevmType determines the address format and which blockchains are compatible:
| VM Type | Compatible Blockchains | Address Format |
|---|---|---|
EVM | POL, BASE, ARB, BSC, OP, ETH, WLD | Ethereum-style (0x...) |
SVM | SOL | Solana-style base58 address |
STK | STK | Starknet-style address |
vmType when created. Duplicate combinations of walletAddress + vmType for the same user are rejected.
Creating a Wallet
Use the Create Wallet endpoint to register a new wallet for a user.Required Fields
vmType: The virtual machine type (EVM,SVM, orSTK)walletAddress: The blockchain addressalias: A friendly name for the wallet (e.g., βMy Polygon Walletβ)
Example
Response
Listing Wallets
Use the List Wallets endpoint to retrieve all enabled wallets for a user.Query Parameters
| Parameter | Required | Description |
|---|---|---|
vmType | No | Filter by VM type (EVM, SVM, STK) |
id | No | Filter by wallet ID |
skip | No | Number of results to skip (pagination) |
limit | No | Maximum number of results to return |
sortBy | No | Sort field (supported: createdAt) |
count (matching results) and total (all wallets for the user) fields for pagination.
Deleting a Wallet
Use the Delete Wallet endpoint to soft-delete (disable) a wallet. Disabled wallets will no longer appear in list results.Using Wallets in Transactions
When creating an on-ramp transaction, thedestinationWalletAddress field specifies where crypto will be sent. You can either:
- Use a saved wallet: Save the wallet first with the Create Wallet endpoint, then reference the address in the transaction.
- Pass the address directly: Provide the
destinationWalletAddressin the Create On-Ramp request without saving it beforehand.
Whatβs Next