Skip to navigation
Embedded Trading

Integration Scenarios

Map common partner business models to the right 6MM embedded trading integration path.
View as Markdown

Embedded trading is usually introduced into an existing product, not launched as a standalone destination. The best integration path depends on where users already spend time and which system owns identity, funds, and operations.

Common scenarios

ScenarioBest starting pointNotes
App or wallet wants a trading entryTrading Widget SDKUse a native or H5 entry point and open the embedded trading experience after user authorization.
Broker or channel platform wants derivatives accessAgent SDK + Trading Widget SDKKeep customer relationship and backend validation in the partner system.
Platform wants a guided trading flowAPI + selected SDK modulesUse backend APIs for account, transfer, and order workflows while exposing only the needed frontend entry.
Existing exchange wants extra marketsLiquidity + API integrationCombine market depth, account workflows, and operational monitoring.

Product decisions before integration

  • Decide whether users enter from a homepage card, asset page, campaign page, or account center.
  • Decide which system owns login state, user eligibility, and country or region availability.
  • Decide how transfers, settlement records, and customer support tickets are shown to users.
  • Decide which events must be forwarded into internal analytics, CRM, or risk operations.
Architecture & Responsibilities

Clarify system boundaries before development.

Trading Widget SDK

Start the embedded frontend path.

Agent SDK

Prepare backend token and webhook flows.