Common EO BROKER Problems and Fixes

Login and access issues

Locked out is the most frequent first complaint, and it is rarely serious. Three causes account for almost all of it, each with a fast and reversible fix.

Being unable to log in feels like an account problem when it is usually an app or address problem. Before assuming the worst, work through the likely causes in order, because the first two solve most cases in under a minute.

1. Confirm you are on the official EO Broker domain or app-store listing. A clone or phishing page will reject correct credentials because it never had your account.
2. Update the app to the current version; an outdated build can fail to authenticate against newer security checks.
3. Expect a new-device verification step if you signed in from a fresh phone or browser, and complete the email or code prompt it sends.
4. Use the in-app password reset rather than guessing, then sign in once and let the app remember the session.

If those steps do not restore access, the issue ties back to verification or a security flag rather than the login screen itself, and that is where support comes in. Keep your registered email reachable, since the new-device and reset flows both rely on it. Bookmarking the real domain is the single best defence against the clone-site version of this problem.

Check the domain, update the app, and complete the new-device prompt before assuming your account is broken.

Deposit hiccups

Funding trouble looks like the app refusing your money, but the refusal often comes from the card issuer. Sorting which side declined the transaction points straight to the fix.

A declined deposit is frustrating because nothing explains why. Splitting the cause between your bank and the payment flow narrows it quickly, and most cases are the bank side.

1. Read the decline message. A bank-side block usually mentions the card or issuer; an app-side issue usually mentions details or limits.
2. Call or message your bank to authorise the transaction, since cross-border or merchant-category blocks on trading payments are common and instantly reversible.
3. Re-enter card details carefully, checking the number, expiry, security code and billing name match the card exactly.
4. If the card keeps failing, switch to an e-wallet, which often clears where a card is blocked, while respecting the method-matching rule for later withdrawals.
5. Confirm the amount meets the entry minimum, roughly USD 10 equivalent and approximate, and any regional limit shown in the app.

Because withdrawals generally route back to the original deposit method, choose a funding method now that you will also be happy to withdraw to later. That one decision prevents a whole class of future withdrawal problems. If every method fails, the account may have a pending verification flag, which links straight to the next section.

Most declined deposits are bank blocks; authorise the card, fix the details, or switch to an e-wallet.

Verification snags

KYC rejections almost never question who you are. They question the photo you sent, and a clean resubmission clears the great majority of stalled verifications.

Identity verification stalls on document quality far more than on identity disputes. The fix is almost always a better image, not an appeal, so resubmit before you escalate.

1. Photograph a current, unexpired government ID in good light, with no glare and the whole document inside the frame.
2. Check that the name, date of birth and any address on the ID match your account details exactly; a mismatch triggers an automatic rejection.
3. If proof of address is requested, send a recent utility bill or statement showing your name and address, dated within the accepted window.
4. Avoid screenshots, scans of scans, or heavily compressed images, which often read as unverifiable.
5. Submit once and wait for the review rather than uploading repeatedly, which can queue duplicate checks.

Completing KYC verification early, right after registration, is the single best move because it removes the most common reason withdrawals are later held. An account that verified on day one rarely meets the stalled-withdrawal complaint at all. If a clean resubmission still does not clear, that is a genuine support case rather than a document problem.

KYC usually fails on image quality, so resubmit a clear, in-date, full-frame ID with matching details.

App and performance

Slow charts, freezes and crashes feel like platform faults but behave like ordinary app problems. The standard mobile fixes resolve most of them in a few minutes.

Performance complaints usually come from the device and connection rather than the servers. Run the routine maintenance steps before concluding the app itself is unstable.

• Update first. An old build is the most common cause of crashes and missing features; install the latest version from the official source.
• Restart and reconnect. Close the app fully, switch between Wi-Fi and mobile data, and relaunch to clear a stalled session.
• Clear the cache or reinstall if charts lag or fail to load; a bloated cache slows the trading terminal.
• Free up resources by closing background apps, since live price streaming and video are memory-hungry.
• Compare to the web terminal. If the browser version runs fine, the problem is local to the app install.

Android users who installed via direct APK should make sure they pulled it from the official source, since an outdated or tampered APK can cause both performance and login problems. If freezes persist across a clean reinstall and a stable connection, capture the details and move to support, which is the next step.

Update, restart, clear the cache and check your connection before treating slowdowns as a platform fault.

Getting help fast

Support moves quicker when you arrive prepared. A short, specific message with the right details attached gets past template replies and to a real answer sooner.

The known friction with support is speed at peak times, template-style replies and the odd language gap. You can route around all three by making your request easy to action on the first read.

1. Choose the right channel: in-app live chat for time-sensitive issues, email or a ticket for anything needing document attachments.
2. State the exact problem, what you already tried, and what you expected, in two or three plain sentences.
3. Attach evidence: a screenshot of the error, your verified account email, and the transaction reference for a deposit or withdrawal.
4. Ask one clear question so the reply cannot deflect into a generic template.
5. Keep the thread in one place rather than opening duplicate tickets, which slows everything down.

For the common cases, you will often have solved the problem yourself before support replies, because login, deposit, verification and performance issues mostly yield to the steps above. Reserve the ticket for genuine account flags, a withdrawal that stays held after KYC is complete, or a confirmed bug. Confirm current terms and contact options in the app, since channels and policies can change.

Arrive with the exact problem, the steps you tried, and screenshots, and pick the channel that matches the issue.