Capital.com "Account Balance Not Available" error
If Autoview rejects a Capital.com command with a log line like Account Balance (EURd) not available. or Account Balance (USDd) not available., the trailing d is the tell: this is happening on a Capital.com Demo connection, and it's Autoview's own check, not Capital.com's. Here's what the message actually means and what to check.
What the error means
Before Autoview sends a Capital.com order, it looks up the balance for the account it's about to trade on, in the currency it expects that account to hold. This error means that lookup came up empty: Autoview couldn't find a balance entry for the currency it was checking against. It's a local, Autoview-side rejection -- the order never reaches Capital.com when this fires, so nothing was attempted and rejected on Capital.com's end.
Why the currency has a "d" on it
Capital.com itself has no currency called EURd or USDd. Autoview appends the d internally, specifically for Demo connections, so a Demo account's EUR balance and a live account's EUR balance can never collide in Autoview's own bookkeeping. A live Capital.com account in EUR shows up to Autoview as plain EUR; the same currency on a Demo connection shows up as EURd. The error message just prints whichever currency it was checking, marker and all, so a Demo-account error always carries the d.
What was already fixed
This exact error was reported in July 2026 on a Capital.com Demo EUR account, and traced to a real mismatch: Autoview's balance lookup was built from the raw currency Capital.com's account API returns (EUR), while the check it ran against expected the Demo-marked version (EURd). Because the two names never matched, every trade failed with this error regardless of the account's real currency. That mismatch was fixed in Autoview's connector code on July 14, 2026, for the ordinary case: one Capital.com Demo connection, no sub-account selected.
A second report came in about three weeks later with the same message on a different currency, USDd. Autoview's Capital.com connector has a second, separate code path that builds the session currency, used specifically when a command selects a particular sub-account with aid= rather than the connection's default account. That second path doesn't apply the same Demo-currency marking the fixed path does, so the same class of mismatch can still occur there. This is a known, still-open report as of this writing, not something this guide can tell you is resolved.
What to check if you still hit it
- Confirm you're on Demo credentials, on the Demo connection. Mixing a live API key into a Demo connection (or the reverse) produces the same symptom, and it's the most common cause by far -- see the troubleshooting section of the Capital.com getting started guide.
- If your command uses
aid=to select a specific sub-account, try it withoutaid=first, on the connection's default account. If that clears the error, the sub-account-selection path is the one still affected. - If neither applies, the mismatch is happening somewhere Autoview's own logs can show but this page can't diagnose from the outside. Contact Autoview support with your connection details and the exact command you sent.
If this doesn't describe your error
This page is specifically about the Account Balance rejection. For Capital.com's own rejections, like an unrecognized epic or an order size below the market's minimum, or for credential and connection errors that aren't currency-specific, see the common error messages reference.