Clarify the pricing and configuration responsibilities shared by a white label broker and its platform provider.
Document who contracts the data source, manages server symbols and approves spread or session changes. A white label storefront should not imply that exchange data rights or infrastructure access automatically transfer from the platform operator.
Collect the platform provider's integration requirements and identify the instruments available to the specific tenant. Agree who receives alerts and who can restore subscriptions after an outage so incidents do not remain between two support teams.
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
| Platform scope | Confirm MT4, MT5 or the actual broker platform and the agreed test environment. |
|---|---|
| Symbol mapping | Review source identifiers, broker suffixes, digits, sessions and missing-symbol behaviour. |
| Adapter ownership | Define which team owns source connectivity, adapter configuration and platform settings. |
| Acceptance | Test ticks, charts, reconnects and the agreed fallback behaviour before production use. |
For your instrument universe, confirm the platform version, server environment and permitted integration path before onboarding. Symbol naming, price precision, sessions and history must remain consistent between the adapter and the platform catalogue.