Deposits

Fund a portfolio wallet and track deposit lifecycle.

After creating a wallet, fund it by sending a supported stablecoin to the wallet’s deposit addresses.

​

Fund the wallet

1. Fetch GET /v2/wallets/{id} and select the returned depositAddresses entry for your funding network. See Supported Chains for accepted stablecoins and network keys.
2. Send the supported stablecoin to that address on the selected network. In the portal, open Deposit funds and select the blockchain.
3. Track the deposit through the deposit APIs or webhooks until it reaches completed and the wallet balance updates.

​

Address readiness

Supported EVM, Solana, TRON, and Stellar deposit addresses are prepared automatically when the wallet is created, independently of its allocation strategy. Stellar account activation and its USDC trustline run in the background. Its deposit address appears once both are ready and deposit monitoring is active. An address is usable once it appears in depositAddresses. Already returned addresses remain usable while setup continues for other networks.

An idle wallet can still be preparing addresses for additional networks. Poll Get Wallet while your intended network’s address is absent. Deposit only after that address appears in depositAddresses.

Funding network	Production address	Sandbox address
Ethereum	depositAddresses.ethereum	depositAddresses.ethereum_sepolia
Solana	depositAddresses.solana	depositAddresses.solana_devnet
Stellar	depositAddresses.stellar	depositAddresses.stellar_testnet
Tempo (USDC.e)	depositAddresses.tempo	Not supported
TRON	depositAddresses.tron	depositAddresses.tron_shasta

See Power Yield for Stellar Balances for the complete Stellar integration flow.

Always validate the token and network before sending. Use the returned address for that network, including when the same EVM address is returned on multiple chains. Supported Chains describes resource funding requirements.

On Tempo, send USDC.e only to depositAddresses.tempo, not the wallet’s Ethereum address. Tempo is production-only. The API reports these deposits as token: "usdc", chain: "tempo", and, once completed, cashPositionId: "cash:tempo:usdc". Deposit monitoring runs every 60 seconds; allow additional time for confirmation and accounting.

​

Minimum amounts

There is no minimum deposit amount. However, small deposits may remain as undeployed cash if deploying them into yield positions is not economically efficient (considering gas costs, minimum trade sizing, and protocol constraints). This minimum is environment-configured and applied per executable rebalance leg: sandbox uses small minimums (e.g. 5 units per leg) so you can test with small amounts, while production minimums are typically higher. See Balances and Yield.

​

Sandbox

Use the supported test token for the network-specific address, including depositAddresses.ethereum_sepolia, depositAddresses.solana_devnet, depositAddresses.stellar_testnet, or depositAddresses.tron_shasta. See Sandbox funding for faucets and test assets.

​

Deposit lifecycle

Status	Terminal	Meaning
processing	No	Ground detected the inbound stablecoin transaction for a workflow-idle wallet or is processing the finalized deposit
completed	Yes	Deposit finalized and posted; wallet balances updated
failed	Yes	Deposit processing failed

Processing deposits are informational until finality. They can appear in deposit and activity APIs shortly after the source wallet broadcasts the transfer when the destination wallet has no active Ground-managed workflow, but they are not included in balance.totalUsd, balance.withdrawableUsd, or positions until ledger posting completes. Wallets with active rebalances, withdrawals, or protocol workflows may wait until final attribution before a deposit appears.

As deposits settle, the wallet’s balance.totalUsd and positions update. Wallets with automatic rebalancing deploy cash toward percentage targets. Otherwise deposits stay in cash until the partner calls /allocate.

​

Deposit response

​

Ethereum Sepolia

{
  "id": "797a5ca3-2a1c-443b-b190-ca951964aa35",
  "walletId": "9d1a1c83-3a1c-4c14-9c5a-0c9a57a4a7db",
  "amount": "10.000000",
  "token": "usdc",
  "chain": "ethereum_sepolia",
  "fromAddress": "0x76f8fc6667e239f83a547d4e16225d6a34f6fa22",
  "txHash": "0xe2e8a534960a7cf19932b35759788a0de4fa131d46d3e36a96a4802b6b93e5e1",
  "status": "completed",
  "cashPositionId": "cash:ethereum_sepolia:usdc",
  "createdAt": "2026-07-09T21:34:17.973Z",
  "completedAt": "2026-07-09T21:34:17.973Z"
}

​

Solana Devnet

Solana responses use base58 addresses and transaction signatures while preserving the same deposit shape:

{
  "id": "797a5ca3-2a1c-443b-b190-ca951964aa36",
  "walletId": "9d1a1c83-3a1c-4c14-9c5a-0c9a57a4a7db",
  "amount": "10.000000",
  "token": "usdc",
  "chain": "solana_devnet",
  "fromAddress": "DmaePN7kL6WjSecMaH4urdS8zN8FwNPTxbdTqFwAw6Fd",
  "txHash": "yTeUkZfSRTRZRdp9UcwRRMtqbeeViAFRWKiTLapi2qPrd7omYfatYsEt2Cak2rFoGDEuLeBPQJPjn7YF88yyWRZ",
  "status": "completed",
  "cashPositionId": "cash:solana_devnet:usdc",
  "createdAt": "2026-07-09T21:34:17.973Z",
  "completedAt": "2026-07-09T21:34:17.973Z"
}

​

TRON

TRON deposits use the same response shape with token: "usdt", chain: "tron" (or "tron_shasta" in sandbox), and a TRON base58 fromAddress. Transaction hashes are hexadecimal without an EVM 0x prefix. Completed deposits identify cash as cash:tron:usdt or cash:tron_shasta:usdt; both belong to the usdt:tron group.

​

Stellar

Stellar deposits use the same response shape with token: "usdc", the environment’s Stellar chain key, and a Stellar G-address. Wait for the Stellar address to appear before sending funds.

Field	Description
id	Unique deposit identifier; when backed by an observed onchain event, the same ID is used from processing through completed
walletId	Portfolio wallet credited by the deposit
amount	Deposit amount as a fixed-precision decimal string
chain	Source chain
token	Deposited token (usdc or usdt)
fromAddress	Sender address (when available)
txHash	Onchain transaction hash
status	Current status (see lifecycle table above)
cashPositionId	Credited cash position ID, or null until the deposit completes
createdAt	When the deposit was first detected
completedAt	When the deposit finalized and posted (null while processing)

​

List deposits

cURL

curl "$BASE_URL/v2/wallets/$WALLET_ID/deposits?limit=25" \
  -H "Authorization: Bearer $GROUND_API_TOKEN"

{
  "data": [
    {
      "id": "797a5ca3-2a1c-443b-b190-ca951964aa35",
      "walletId": "9d1a1c83-3a1c-4c14-9c5a-0c9a57a4a7db",
      "amount": "10.000000",
      "token": "usdc",
      "chain": "ethereum_sepolia",
      "fromAddress": "0x76f8fc6667e239f83a547d4e16225d6a34f6fa22",
      "txHash": "0xe2e8a534960a7cf19932b35759788a0de4fa131d46d3e36a96a4802b6b93e5e1",
      "status": "completed",
      "cashPositionId": "cash:ethereum_sepolia:usdc",
      "createdAt": "2026-07-09T21:34:17.973Z",
      "completedAt": "2026-07-09T21:34:17.973Z"
    }
  ],
  "nextCursor": null
}

Supports cursor-based pagination. See API Conventions.

​

Fetch a deposit by ID

curl "$BASE_URL/v2/wallets/$WALLET_ID/deposits/$DEPOSIT_ID" \
  -H "Authorization: Bearer $GROUND_API_TOKEN"

​

Look up by transaction hash

curl "$BASE_URL/v2/wallets/$WALLET_ID/deposits/lookup?txHash=$TX_HASH" \
  -H "Authorization: Bearer $GROUND_API_TOKEN"

Optionally scope to a specific chain:

curl "$BASE_URL/v2/wallets/$WALLET_ID/deposits/lookup?txHash=$TX_HASH&chain=arbitrum" \
  -H "Authorization: Bearer $GROUND_API_TOKEN"

​

Deposit webhooks

Subscribe to portfolio_wallet.deposit.status_changed for real-time deposit tracking. See Webhooks.

​

Next steps

• Balances and Yield — track how deposits are allocated and earning yield
• Withdraw Funds — withdraw USDC or USDT from the wallet
• Webhooks — subscribe to deposit status events