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

# Architecture & Responsibilities

A clean embedded trading launch depends on clear responsibility boundaries. Partner systems should keep sensitive business ownership, while 6MM provides the trading infrastructure and lifecycle capabilities.

<h2 id="responsibility-model">
  Responsibility model
</h2>

| Area                | Partner system                                                                         | 6MM infrastructure                                                                           |
| ------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| User relationship   | Owns the user account, login state, customer support identity, and eligibility checks. | Receives validated trading entry context and maintains trading-side state.                   |
| Secrets and signing | Stores partner API keys on the backend and signs server-side requests.                 | Verifies signed requests and processes authorized actions.                                   |
| Trading experience  | Provides entry points, navigation, and product context.                                | Provides trading UI, order lifecycle, market data, positions, risk, and settlement behavior. |
| Operations          | Handles support workflows, business analytics, and internal escalation.                | Emits events, webhooks, and status information needed for integration.                       |

<h2 id="production-principles">
  Production principles
</h2>

* Keep all partner secrets on the backend.
* Treat embed tokens as short-lived entry credentials.
* Process webhooks idempotently and store event IDs.
* Use monitoring around token issuing, transfer flows, and order-state changes.
* Keep customer-facing copy consistent across entry, trading, and support pages.

<h2 id="related-docs">
  Related docs
</h2>

Review backend authentication expectations.

Understand signed API calls.

Handle event delivery safely.