Compatibility and scenarios

Module compatibility

The table below shows how each feature module behaves under each identity option.

Feature module	SSO user creation and authorisation	One-time token handoff
Embedded cTrader web	Compatible	Not compatible
In-app deposit/withdrawal	Compatible	Compatible
In-app KYC	Compatible	Compatible
In-app generic action/chat	Compatible	Compatible
In-app ribbons	Compatible	Not compatible
cTrader Invite	Compatible	Compatible
Identity only (no feature module)	Compatible	Compatible with limitations

Use cases

Minimal deployment

Add a cashier or KYC flow to cTrader with the smallest possible integration footprint.

• Identity: One-time token handoff
• Modules: In-app deposit/withdrawal and/or In-app KYC
• Constraint: Spotware remains the identity provider. The broker does not control the login experience.

Broker-owned identity

The broker controls user creation, login and session management. cTrader Web runs inside the broker client area.

• Identity: SSO user creation and authorisation
• Modules: Embedded cTrader web, any compatible feature module
• Constraint: Requires OAuth implementation in the broker CRM.

Full deployment

All compatible feature modules run under a single broker-owned identity layer.

• Identity: SSO user creation and authorisation
• Modules: All compatible feature modules
• Constraint: Highest implementation complexity. Requires a mature CRM with OAuth support.

Regulated compliance

The broker owns KYC data and maintains a complete compliance audit trail.

• Identity: SSO user creation and authorisation
• Modules: In-app KYC, optionally In-app deposit/withdrawal
• Constraint: The broker is responsible for KYC data storage and re-verification workflows.

Migration path

One-time token handoff can serve as a starting point before migrating to SSO. Feature modules deployed under One-time token handoff remain compatible after migration: no redeployment is required for them.

1. Deploy One-time token handoff with the required feature modules.
2. Build OAuth support in the broker CRM.
3. Migrate to SSO user creation and authorisation.
4. Add the modules that require SSO user creation and authorisation: Embedded cTrader web and In-app ribbons. Feature modules already deployed under One-time token handoff continue to work with no redeployment.