Multi-module bundles
Recommended module combinations for common deployment scenarios.
note
Brokers may implement any valid module combination; these bundles are guidance, not requirements.
Predefined bundles
- Full suite
- Compliance-ready cashier
- Affiliate-driven deposit
- Engagement-focused
Implement the following modules:
Option A: Broker-owned identity
Implement the following modules:
Option B: cTrader identity provider
Implement the following modules:
Implement the following modules:
Implement the following modules:
Bundle selection guide
Decision matrix
| Business priority | Recommended bundle | Implementation complexity |
|---|---|---|
| Regulatory compliance | Compliance-ready cashier | Medium |
| Partner growth | Affiliate-driven deposit | High |
| User experience | Engagement-focused | Medium |
| Enterprise needs | Full suite | High |
Bundle customisation
Module substitution options
Identity module substitution
- SSO user creation and authorisation → One-time token handoff: Reduce complexity
- One-time token handoff → SSO user creation and authorisation: Increase control and branding
Feature module substitution
- In-app deposit/withdrawal → In-app generic action/chat: Replace deposit focus with support focus
- In-app ribbons → cTrader Invite: Replace messaging with partner attribution
- Embedded cTrader web → In-app KYC: Replace embedded trading with KYC focus
Phased implementation
Phase 1: Foundation
- Read first: All prerequisites documentation
- Choose: SSO user creation and authorisation or One-time token handoff
Phase 2: Core features
- Select 1–2 core feature modules based on business priorities
Phase 3: Expansion
- Add additional feature modules
Phase 4: Advanced features
- Optimise existing implementations and scale across user base