PropTector Book a call
§ Platform · 04 Modules

Four modules. One system.

Risk detection, payout review, training, and automation — integrated end-to-end so your ops team stops stitching tools together.

§ 01 · Risk Detection

Risk Detection.

Every fill, every funded account, every known abuse pattern — reviewed the moment it happens. No dashboards to check. No reports to cross-reference. Signals surface to the operator who can act on them.

How it works
01 · Ingest

Broker-bridge streaming

Trades arrive in real time from your MT4/MT5/cTrader bridges. Nothing batched, nothing polled.

02 · Score

Pattern engine

Each fill is scored against nine abuse patterns and cross-referenced across accounts for coordinated behavior.

03 · Surface

Operator alert

High-confidence hits surface to the risk queue with evidence, related accounts, and a recommended action.

What it catches
Copy trading

Clusters of accounts taking the same positions, often within 200ms of each other, across different IPs.

Martingale

Doubling-down patterns after losses, typically paired with widened stops and no defined take-profit.

News abuse

Entries placed inside the locked window around scheduled high-impact events — NFP, CPI, FOMC.

Grid strategies

Stacked orders at fixed pip distances around a price level, regardless of direction.

Self-hedging

Opposing positions across linked accounts that net to a guaranteed payout regardless of market direction.

Gambling behavior

Lot-size escalation, session-end panic trades, or position sizing wholly uncorrelated with account equity.

Latency< 400ms p99
Patterns9 tracked · extensible
IngestMT4 · MT5 · cTrader · Match-Trader
CorrelationIP · Device · Fingerprint · KYC
EvidenceFull trade log · Replayable
Retention13 months hot · Archive after
§ 02 · Payout Review

Payout Review.

Every payout request ships with a full windowed assessment. Your team sees a verdict, the evidence, and the precedent — all before they click approve.

How it works
01 · Window

Assessment window

Every trade between the previous payout (or funding) and the current request is pulled into review.

02 · Score

Behavior scoring

Pattern hits, strategy fit, drawdown profile, and consistency are scored and weighted against firm rules.

03 · Verdict

Four-way recommendation

Approve, deduct, escalate, or reject — with the evidence attached and a defensible audit trail.

What it produces
Approve

No pattern hits. Strategy within declared rules. Payout clears straight to treasury.

Deduct

Partial violations. Specific trades stripped from eligible PnL, rest paid out.

Escalate

Ambiguous signal — routed to senior risk with full context for a human call.

Reject

Clear abuse pattern or rule breach. Request denied with documented reasoning.

Audit trail

Every verdict, every input, every edit — timestamped and immutable for regulatory review.

Precedent matching

Similar cases surfaced at review time so decisions stay consistent across operators.

VerdictsApprove · Deduct · Escalate · Reject
WindowPer-request · Configurable
Audit logImmutable · Exportable
IntegrationsTreasury · CRM · Email
§ 03 · Training

Training.

Risk training for the team making the calls. Support training for the team answering the tickets. Operators who know the terrain before they step on it.

How it works
01 · Curriculum

Role-scoped modules

Separate tracks for risk analysts and support staff — each calibrated to what that role actually does.

02 · Practice

Live-fire case studies

Anonymised real cases from PropTector's detection archive — trainees call the verdict, then see what happened.

03 · Certify

Competency sign-off

Measured scoring against the standard. Operators certify; firms get documentation.

What you get
Risk analyst track

Pattern recognition, verdict reasoning, precedent use, escalation judgement.

Support track

Trader-facing answers for denied payouts, strategy questions, and rule disputes without undermining the call.

Onboarding path

New hire to first independent verdict in 3 weeks, mapped step by step.

Certification records

Signed-off competency documentation for regulators and partner relationships.

TracksRisk · Support
FormatAsync modules + live clinics
Case archive400+ anonymised cases
OutputCertificates · Transcripts
§ 04 · Automation

Automation.

The manual grind your ops team shouldn't be doing — emails, CRM updates, reporting handoffs — moved to pipelines that just run.

How it works
01 · Trigger

Event-driven pipelines

A verdict, a breach, a payout clearing, a new funded account — every meaningful state change is a trigger.

02 · Route

Destination logic

Events fan out to email, CRM, reporting warehouse, or ticketing system based on firm-configured rules.

03 · Confirm

Delivery receipts

Every hop logged. Failed deliveries retried and surfaced so nothing silently goes missing.

What it produces
Email workflows

Trader-facing emails for verdicts, funding steps, rule breaches — templated and firm-branded.

CRM integrations

HubSpot, Salesforce, Attio — accounts and events synced so your sales + success teams see the same data.

Reporting pipelines

Daily, weekly, or event-triggered reports piped to your warehouse, Slack, or a PDF in your inbox.

Ticketing handoff

Escalations arrive in Zendesk, Intercom, or Linear with all the context already attached.

TriggersVerdicts · Breaches · Payouts · Funding
DestinationsEmail · CRM · Warehouse · Tickets
DeliveryRetried · Logged · Receipted
Rate limitPer-firm throttles · Burst-safe
Ready to talk

See the platform end to end.

30 minutes. Screen-share. We'll run through all four modules against your actual use cases.

Book a call