Handling Wallet Balances

​

Recommended Sync Strategy

• value: The human-readable string representation of the verified balance, pre-formatted to match token decimals.
• rawValue: The raw integer string representation in minimal base units (atomic units/wei/lamport/satoshi/sun).

​

Samples

{
 "requestId": "....",
 "method": "wallets:''.''",
 "params": {
   "...",
   "wallet":{
	  "id":"69eba664a8d8bc8c594d17fd",
	  "address":"0x7A750D8D6e12cce09A7c15482077a8A4d4c37de4",
	  "type":"settlement",
	  "protocol":"EVM",
	  "name":"Default Wallet(EVM)",
	  "refId":"b2be0f63-f73e-49f5-bc52-93dae008b1d7",
	  "custodyType":"DEVELOPER",
	  "token":{
	    "name":"Euro Coin",
		"symbol":"EURC",
		"blockchain":"BASE",
		"tokenAddress":"0x808456652fdb597867f38412077a9182bf77359f",
		"isNative":false,
		"decimals":6,
		"standard":"ERC20",
		"balance":{
			"value":"20",
			"rawValue":"20000000"
		    }
		 }
	   }
	}
  }
}

​

Why Use params.wallet.token.balance?

1. State Overwriting: Replacing local database values with the payload state guarantees absolute alignment with the on-chain ledger at transaction execution time.
2. Re-org Protection: In the event of a chain re-organization, subsequent state updates automatically correct local records without requiring manual database reconciliation.
3. Multi-Source Consistency: Overwriting state avoids race conditions when multiple transactions occur in close succession across automated wallet workflows.