Bottom Line
Rule-disciplined traders who can follow payout and risk constraints without exceptions.
DECRYPTING OMEGA INTEL
Accessing secure database... Fetching real-time risk parameters and slippage reports.
Finanslab Co. Prop Omega
MyCryptoFunding
Last reviewed: 28.03.2026
Trustpilot 4.3Payout outlook RED
Rule-disciplined traders who can follow payout and risk constraints without exceptions.
FinansLab Score
Verified24/100
Internal rating
High RiskGrade F
1A. Evidence strength
How strong is the available evidence?
Firms may not publish direct payout proof. This block shows evidence strength using available official and community signals.
High evidenceScore 100/100
Official confirmation
6 official source links mapped for this profile.
Community reports
1 active complaint signal in the current sample.
Consistency across sources
No major conflict between mapped sources.
Last updated
28.03.2026
1B. Trader checkout snapshot
What matters before you buy this challenge
Use these six fields for a fast pre-check before visiting the official checkout page.
| Max DD | 10% |
| Daily DD | 10% |
| Trailing / Static | Trailing |
| Reset Time | Not verified yet |
| Min Trading Days | 5 days |
| Payout Cycle | Standard funded payout request cycle is every 15 traded days (unless specific payout addon terms override). |
MyCryptoFunding model matrix (plain view)
| Track | Target | Drawdown | Min days | Payout start | Key point |
|---|---|---|---|---|---|
| Evaluation (2-Step) | Phase 1 + Phase 2 targets (program based) | Program-based daily and max loss limits | Common baseline: at least 3 trading days per phase | After funded-stage eligibility is met | Use policy page numbers as final source before buying |
| Funded account | No new evaluation target | Funded risk limits continue to apply | Depends on active payout policy | Cycle-based request flow (policy-dependent) | Keep account flat and compliant before payout request |
MyCryptoFunding payout and rule checks
| Simple model | Think in two blocks: pass 2-step evaluation, then follow funded payout rules. |
| Split reality | 80% is the stable baseline in core docs. "Up to 100%" appears as conditional marketing language. |
| Method check | Listed methods include crypto, card, and PayPal. Availability can change by region/policy. |
| Platform check | MCF Platform (TradingView-linked) and MT5 are listed. Verify your account route before execution. |
| Hedging check | Same-account hedging can be allowed, but cross-account opposite-position behavior can be restricted. |
| Compliance gate | KYC, jurisdiction, and policy compliance checks can block payout even with positive PnL. |
Official SummaryToggle
Most critical summary (short)
- •My Crypto Funding is easy to start, but FAQ alone is not enough for final rule decisions.
- •The main confusion point is split language: 80% baseline vs up-to-100% marketing copy.
- •The biggest practical risk is reading promo text as binding policy.
- •Social signal here is mostly isolated payout allegations, not a heavy repeated complaint wave.
Source-based summary
Onboarding and model structure
- •Flow is simple: choose model/platform/size, then run Phase 1 and Phase 2.
- •FAQ says there is no time limit if rule compliance is maintained.
- •Pass path is clear in copy: finish both phases, then move to funded.
Payout and legal framing
- •Split is shown as 80% in core FAQ text, but up-to-100% appears in marketing sections.
- •Simulation and non-regulated-service disclosures are clearly stated in legal notes.
- •Final decisions should use Terms, payout policy, and jurisdiction pages.
Risk and platform boundaries
- •Same-account hedging is allowed, but cross-account opposite hedging is restricted.
- •Platform pages focus on features and should not be treated as hard rule source.
- •Social sample shows isolated payout complaints, with weak signal in other complaint categories.
Practical checklist
- •Read Terms and payout policy fully before starting the challenge.
- •Treat contract terms as final when split wording differs across pages.
- •Apply hedging rules exactly as written for same-account and cross-account cases.
- •Use FAQ for onboarding only, then confirm hard limits in policy documents.
- •Keep records of payout requests and support messages if a dispute appears.
Key Terms ExplainedToggle
Flat Account
No open positions at withdrawal request time. If positions are open, withdrawal action may stay locked.
Daily Drawdown
Maximum allowed daily loss. It resets at a defined server time; breach can trigger hard failure.
Max Drawdown
Total loss boundary on the account path. Breach can terminate progression and payout eligibility.
Relative / Static
Relative drawdown can trail high-water marks; static drawdown stays fixed to the baseline level.
Hard Breach
Immediate rule-failure state that can close account path. Common triggers: daily DD, max DD, symbol loss.
User complaints & reports sent to FinansLab
Complaint list
No major verified complaint cluster in the March 2026 sample for this profile.
FinansLab March 2026 sample • Monitoring • Neutral
Latest social-check timestamp is stale; complaint signals may be incomplete.
FinansLab freshness guard • Needs refresh • Neutral
"This section summarizes user commentary. Before making a final decision, review the official contract terms and firm policy documents."