Embedded Trading

Architecture & Responsibilities

Clarify what the partner system owns and what 6MM infrastructure provides in embedded trading deployments.
View as Markdown

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.

Responsibility model

AreaPartner system6MM infrastructure
User relationshipOwns the user account, login state, customer support identity, and eligibility checks.Receives validated trading entry context and maintains trading-side state.
Secrets and signingStores partner API keys on the backend and signs server-side requests.Verifies signed requests and processes authorized actions.
Trading experienceProvides entry points, navigation, and product context.Provides trading UI, order lifecycle, market data, positions, risk, and settlement behavior.
OperationsHandles support workflows, business analytics, and internal escalation.Emits events, webhooks, and status information needed for integration.

Production principles

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

Review backend authentication expectations.

Request Signing

Understand signed API calls.

Webhook Security

Handle event delivery safely.