UNIFIED is an account model, not only a Spot wallet

Bybit Unified accounts can combine Spot assets, derivatives collateral and liabilities. The connector uses the V5 wallet balance contract for UNIFIED and does not claim that a separate Funding wallet is included. Products should display the provider and account scope so a user can compare the same boundary in Bybit.

Keep the Bybit key read-only

A portfolio integration needs account or asset visibility but not SpotTrade, ContractTrade, transfers or withdrawals. Create a dedicated key, validate its read-only state and submit it only from your server-side flow. If the provider rejects scope or IP restrictions, surface a specific connection error rather than requesting broader permissions.

Wallet balance and availability are not interchangeable

Bybit exposes wallet balance, locked amount, borrow amount and account-level availability. Legacy per-coin free fields do not retain the same meaning for Unified accounts. The normalized model reports what the provider supports and avoids manufacturing a traditional free quantity that could misstate collateral or liabilities.

Centralize refresh and inspect partial results

Bybit synchronization should run through one backend job path with bounded retries and provider-aware rate handling. After refresh, read connection status and normalized balances rather than asking the browser to call Bybit indirectly. Performance may be partial when transfer history or historical pricing cannot cover Unified activity.

Account type explains many apparent discrepancies

Confirm that the user connected the intended Unified account and compare liabilities as well as positive assets. Funding balances are outside the current scope. Treat missing history, unsupported wallet types and provider permission errors as explicit states so support does not diagnose them as generic arithmetic problems.