Skip to content
FPTHelp Center

Reporting a Problem or Bug

How to report an FPT bug so it can be reproduced and fixed, what belongs in the report, and why exploiting a pricing or data fault instead of reporting it is a breach.

Version
v1.0
Effective
2026-08-04
Last updated
2026-08-04
Applies to
Every FPT account, before and after launch
Contents (7 sections)

Report bugs to support@fundedpredictiontrader.com. A report that can be reproduced gets fixed; a report that says "it broke" usually produces an exchange of questions instead of a fix.

The sections below are the whole method: check it is really a bug, capture what happened while it is still on screen, then send one message containing all of it.

First, Rule Out the Expected

Some things look like faults and are not:

Capture It Before It Disappears

  1. Screenshot the whole window, not a crop of one number. The surrounding page carries the state we need.
  2. Copy the exact error text. Type it out rather than describing it.
  3. Note the timestamp — date, time and your time zone. Without it, logs cannot be matched to your report.
  4. Note where you were: the page or screen, and the market or account involved.
  5. Try to reproduce it once. Whether it happens again is itself a useful fact, and "consistently reproducible" is the single most valuable sentence in a bug report.
  6. Try a private window and a second browser. A fault that disappears in a clean window is usually a cache or extension problem, which is still worth reporting but is fixed differently.

What to Put in the Report

  • Your FPT account email and, where the issue involves a purchase, your order ID.
  • One sentence on what you expected, and one on what actually happened.
  • The numbered steps to reproduce it, starting from signing in.
  • Date, time and time zone, and how many times it has happened.
  • Device, operating system and browser, including version, and whether you were on desktop or mobile.
  • Your network, if it is unusual — corporate, school, public wifi or a VPN.
  • Screenshots. Attach them; do not describe them.

Never Trade a Bug

If you find a fault that appears to give you an advantage — a stale or wrong price, a mispriced market, a limit that fails to apply, a balance that moves incorrectly — stop trading it and report it.

Exploiting a pricing error, a data-feed fault, a latency artefact or a platform defect is prohibited conduct and is a breach of the program, regardless of whether you believed it was intentional. Profit produced that way is not recognised. See Price and Data-Feed Exploitation and Good-Faith Trading and Prohibited Conduct, both of which are incorporated into the FPT Scale Program Agreement.

Reporting a fault promptly is the correct action and is treated as such. Repeatedly trading one is not an oversight anyone will read as accidental.

Security Issues

If you find something that looks like a security vulnerability — a way to see another customer's data, bypass a control, or act on an account that is not yours — report it privately to support@fundedpredictiontrader.com and do not post it publicly, do not test how far it goes, and do not access anyone else's data to demonstrate it. Describe what you found and stop there.

Feature Requests and Feedback

Ideas are welcome at the same address. Mark them clearly as feedback rather than a fault so they are routed to product rather than triage. FPT does not promise that any request will be built and does not give a timeline for one.

Still Need Help?

Email support@fundedpredictiontrader.com with your FPT account email, your order ID where relevant, what you saw, what you expected, numbered steps to reproduce, the date, time and time zone, and your device and browser. Attach the full-window screenshot. FPT does not publish a guaranteed response time, but a complete first message is what removes the round trip.

Was this helpful?

Related articles

Need a person?

Email support@fundedpredictiontrader.com with your account email and order ID, or open a request from your dashboard.