> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.6mm.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.6mm.com/_mcp/server.

# Integration Scenarios

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.

<h2 id="common-scenarios">
  Common scenarios
</h2>

| Scenario                                            | Best starting point            | Notes                                                                                                      |
| --------------------------------------------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------------- |
| App or wallet wants a trading entry                 | Trading Widget SDK             | Use a native or H5 entry point and open the embedded trading experience after user authorization.          |
| Broker or channel platform wants derivatives access | Agent SDK + Trading Widget SDK | Keep customer relationship and backend validation in the partner system.                                   |
| Platform wants a guided trading flow                | API + selected SDK modules     | Use backend APIs for account, transfer, and order workflows while exposing only the needed frontend entry. |
| Existing exchange wants extra markets               | Liquidity + API integration    | Combine market depth, account workflows, and operational monitoring.                                       |

<h2 id="product-decisions-before-integration">
  Product decisions before integration
</h2>

* 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.

<h2 id="recommended-next-steps">
  Recommended next steps
</h2>

Clarify system boundaries before development.

Start the embedded frontend path.

Prepare backend token and webhook flows.