How is drawdown calculated?
On equity or on balance, static or trailing from the high-water mark, depending on the program's configuration.
A challenge engine shaped around your program
The challenge engine decides who passes, who is funded and who is stopped. Finteractive builds it as a precise, transparent rules system that your traders trust and your risk team controls.
What a challenge engine does
It watches every account against the rules of its phase, advances traders who qualify, provisions funded accounts and records every decision.
Rule types
- Daily loss limits, fixed or relative to the day's starting equity
- Maximum drawdown, static or trailing from the high-water mark
- Profit targets per phase
- Consistency rules across trading days
- Minimum trading days and time windows
- Instrument, news and hedging checks
Equity and balance calculations
Drawdown can be measured on equity, including floating profit and loss, or on balance. The engine supports both models, and the choice is a setting per program, so trader-facing rules and engine behaviour always match.
Real-time checks
Checks run continuously against live account data. Continuous evaluation catches a breach in the moment it happens, which keeps outcomes fair and disputes short.
Phase transitions and provisioning
When a trader passes, the next account is created and funded automatically, credentials are delivered and the portal updates. Configuration drives the journey, so launching a new program is a setup task.
Audit trail and disputes
Every evaluation, breach and transition is stored with the data that triggered it. Support can answer a trader's question with evidence in seconds.
How we deliver
- 01
Architect call
A thirty-minute conversation with an engineer who has built comparable systems. The goal is a shared picture of the product and its constraints.
- 02
Scope and architecture
The senior team turns the conversation into a scoped plan, an architecture and a delivery path the client can review.
- 03
Build in increments
Working software is shown early and often. The client sees real progress and steers priorities along the way.
- 04
Launch and harden
Release, monitoring and performance tuning, with the same team that built the product on hand.
- 05
Evolve
New markets, instruments, payment rails and features are added by the team that knows the system best.
Questions and answers
Why do real-time checks matter?
Continuous evaluation catches breaches the moment they happen, which keeps results fair and reduces disputes.
Can rules change while the program is live?
Rules are configuration. New programs and rule changes are applied as settings.
How are disputes handled?
Each decision is stored with the data behind it, so support can show exactly what happened and when.
Guides
Talk to an architect
Thirty minutes. You speak with an engineer who has built it before.
Book a technical call