guide

When trading support asks to share your screen, pause before granting access

Understand the difference between explaining an error and exposing a device, and keep a clear record if an unexpected support contact raises concerns.

By Reviews4Friends Editorial Team ·

Updated Oct 5, 2026

A caller who offers to fix a trading-app problem may sound helpful, especially when a payment is delayed or a login fails. But showing a screen or handing over remote control changes what that person can see and possibly do. The FCA identifies unexpected requests for screen sharing or remote access as a warning sign. A familiar logo or a professional voice is not enough to authenticate the request.

Describe the problem without exposing the whole device

The first useful information is often a short description: which service, which action, the time and the exact non-sensitive error message. That does not require revealing a bank login, one-time code or full account statement. A screenshot can also contain unrelated private material, including open tabs and notifications. Before sharing any diagnostic item through a verified route, consider what information it actually adds to the explanation.

Describe the problem without exposing the whole device
Requested actionWhy it matters
Share the whole screenOther financial or personal information may be visible
Grant remote controlAnother person may operate the device
Read an authentication code aloudA code can authorise access or an action
Use a link supplied by the callerThe destination has not been independently authenticated

Verify the contact separately

End the unexpected interaction and use a contact route found independently from the relevant service or regulator record. Do not use the caller’s reassurance as the verification step. An authentic software name does not authenticate the person asking you to install or open it. The question is who is receiving access and why that access is needed, not whether the tool itself is widely used.

Imagine a fictional caller who knows the name of a broker and the approximate date of a deposit. Those details may make the call persuasive, but they do not prove the caller controls the broker’s legitimate support channel. If the proposed fix suddenly requires opening online banking while the caller watches, the scope has changed. A request about a trading interface has become a request to expose another financial account.

If access has already been granted

Stop the session and contact the affected financial provider promptly through a trusted route if account access or payments may be at risk. Use a separate trusted device where appropriate to seek help. Preserve the contact details, messages, timing and a concise description of what was visible or done. Do not continue a suspicious session just to collect more evidence, and do not publish passwords, codes or identity documents in a complaint post.

Separate what you observed from what you fear happened. For example, a remote-control session occurred is an observation; money must have been transferred is a question until account records establish it. The distinction helps the provider investigate quickly. The Ombudsman describes routes for complaints about how financial businesses handled unauthorised payments or identity theft, but eligibility and outcome depend on the facts. No refund is promised here.

Keep the explanation practical

This guide is not a finding against a named company or a ban on every form of technical support. It is a way to recognise when an unexpected request exposes more than the original problem requires. A clear error description, independent contact verification and prompt reporting of suspected account compromise are more useful than trusting a caller’s urgency.

The same identity discipline applies when a friend introduces an app. When an online friend introduces trading

Article sources

  1. Screen sharing scams ↗ Financial Conduct Authority
  2. Unauthorised payments and identity theft ↗ Financial Ombudsman Service