Scalper-Proof Without Drama: A Broker’s Playbook for Tick Scalping Controls

Tick scalping isn’t “bad trading” — it’s a mismatch between a broker’s execution setup and a client’s microstructure strategy. When traders repeatedly capture tiny price changes faster than your pricing and hedging chain can respond, the result is predictable: higher LP rejects, negative slippage for the broker, and a spike in complaints when you react too aggressively.

This post is a practical playbook: how brokers detect tick scalping, how they price it (without quietly changing the deal), and when it’s reasonable to block or restrict it — while keeping client disputes and regulatory risk under control.

1) What brokers mean by “tick scalping” (and why it becomes a dispute)

In broker ops, “tick scalping” usually describes ultra-short holding-time trading that targets micro-moves (often 0–2 pips) and depends on execution speed, quote updates, and fill logic more than directional market views. It overlaps with terms like latency arbitrage, toxic flow, and quote sniping.

Disputes happen when the broker treats tick scalping as “abuse,” but the client sees it as legitimate scalping. The gap is often caused by unclear definitions in the execution policy and inconsistent treatment across accounts.

Operationally, tick scalping becomes expensive when it:

• Increases LP rejection/last-look rejects and partial fills
• Creates systematic adverse selection (clients win when you can’t hedge fast enough)
• Forces you to widen spreads or increase markups for everyone, hurting conversion

2) How brokers detect tick scalping: the signals that actually matter

You don’t detect tick scalping from one metric. You detect it from a profile built from execution and behavior data. The best setups combine platform logs (MT4/MT5/cTrader), bridge/aggregator stats, and LP execution reports.

Core indicators to track (per account, per symbol, per session):

• Median holding time (e.g., < 20–60 seconds is a common red flag band)
• Trade-to-deposit ratio and orders per minute bursts
• Average take-profit distance (very small TP, frequently 0.5–2.0 pips)
• Win rate vs. average win size (high win rate with tiny average win can be a tell)
• Slippage distribution (client consistently gets positive slippage vs. your book)
• Fill quality vs. market volatility (profits cluster around fast ticks, not trends)

Execution-chain indicators (often more predictive than trading stats):

• Reject rate and requote rate upstream (bridge/LP)
• Time-to-fill and quote age at fill (ms)
• Markout (price movement after fill, e.g., +250ms / +1s). Persistent negative markout for the broker is classic toxicity.

Tip: segment by symbol + session. A trader who “scalps” EUR/USD during London open may be normal; the same behavior on thin minors at rollover can be a different risk profile.

3) Price it first: turning “block scalpers” into a transparent commercial model

Blocking is the loudest lever — and the one most likely to create disputes. A cleaner approach is to price the behavior in a way you can defend.

Common pricing responses brokers use (choose what matches your liquidity and risk model):

• Account-type segmentation: offer a “Raw/ECN” account with explicit commissions and realistic execution expectations, and a separate “Standard” account with markup and protective execution logic.
• Symbol- and time-based markups: widen markups only where your LP depth is thin or rejects spike (exotics, rollover, news windows). Keep it rule-based and disclosed.
• Minimum commission / per-lot fees for ultra-high-frequency micro tickets (especially when operational costs are driven by message rates).
• Dynamic risk routing: route suspected toxic flow differently (e.g., more conservative A-book paths, different LP pools, or internalization thresholds) rather than changing the client-facing price.

To reduce disputes, align pricing changes with documents clients can see:

• Clear product specs (contract size, commission, minimum distance if any)
• Published execution policy (how fills, slippage, and rejects are handled)
• A versioned terms update log (date-stamped)

If you can’t explain a change in one paragraph to a client, expect the ticket volume to rise.

4) If you must restrict: “soft blocks” that are defensible and less inflammatory

Sometimes pricing isn’t enough — especially if LPs threaten to cut terms, or your reject rate makes the product unreliable. In those cases, use restrictions that are objective, measurable, and consistently enforced.

Examples of “soft blocks” (less dispute-prone than outright banning):

• Max order rate / throttling per account (message-rate controls)
• Minimum holding time for specific account types (more common in prop evaluations than in retail brokerage)
• Minimum distance for SL/TP on specific symbols during specific sessions (use sparingly; it’s visible)
• Reduced max leverage or reduced max lots for accounts that trigger toxicity thresholds
• Execution mode changes for flagged accounts (e.g., move to an account type with different execution expectations)

The dispute-minimizing rule: avoid retroactive enforcement. If you introduce a minimum holding time or throttling, apply it prospectively and document the effective date.

Also, be careful with broad labels like “arbitrage.” Unless you can evidence a specific exploit (e.g., systematic latency advantage vs. your quote source), keep the language neutral: “order rate limits,” “execution stability controls,” “liquidity protection.”

5) The “no-surprises” dispute framework: what to log, what to show, what to say

Most scalping disputes aren’t won on opinions — they’re won on logs and consistency. Your goal is to show that (a) execution worked as described, and (b) your actions were policy-based, not discretionary punishment.

Minimum evidence pack to retain (and be able to export quickly):

• Order lifecycle timestamps: client send time, server receive, bridge route, LP ack/fill/reject
• Top-of-book quotes around the fill (your aggregated feed snapshot)
• Slippage and reject statistics for the account and for the symbol/session baseline
• Any applied risk flags: threshold crossed, date/time, rule ID

Client-facing explanation template (keep it short):

• What happened: “Your account triggered our order-rate/holding-time threshold on X date.”
• Why it matters: “This pattern increases reject rates and execution instability on our liquidity chain.”
• What we changed: “We moved you to Account Type Y / applied order-rate limits / adjusted symbol conditions per published specs.”
• What you can do: “Trade on Account Type Z designed for high-frequency execution / reduce order rate / avoid rollover windows.”

Regulatory note: execution and fairness expectations vary by jurisdiction and license type. Always check local regulations and ensure your execution policy, marketing claims (e.g., “ECN”), and actual routing behavior are consistent.

6) Operational checklist: implement tick-scalping controls without breaking conversion

Below is a practical sequence that keeps ops, dealing/risk, and support aligned.

Step 1 — Baseline your execution reality (2 weeks of data):

• Reject/partial fill rates by LP, symbol, and session
• Markout and slippage distributions
• Ticket sizes and order rates

Step 2 — Define toxicity thresholds you can defend:

• Holding time threshold (per account type)
• Order rate threshold (per minute)
• Markout threshold (e.g., persistent negative markout)

Step 3 — Choose the least aggressive lever first:

• Pricing/account segmentation → routing changes → throttling → explicit restrictions → closure (last resort)

Step 4 — Update client documents and support macros:

• Execution policy wording (plain language)
• Product specs (symbol conditions, commissions, limits)
• Support scripts + escalation path

Step 5 — Monitor outcomes:

• Did reject rates drop?
• Did disputes increase?
• Did conversion/retention change on “raw vs standard” accounts?

If disputes rise after a control change, it’s usually a messaging/policy clarity problem — not a risk logic problem.

The Bottom Line

Tick scalping becomes a broker problem when it creates toxic flow, LP rejects, and unstable execution — not because it’s “fast trading.” Detect it using execution-chain metrics (rejects, quote age, markout), then price or segment it transparently before you block it.

When restrictions are necessary, use objective thresholds, apply them prospectively, and keep a tight evidence pack for dispute handling. If you want to implement scalable detection, routing, and policy-aligned controls in your backoffice stack, start here: /get-started.