Reference · CRM Account Operations
Client, Wallet and Trading Account IDs: Mapping Records
Map client profiles, wallets and trading accounts using stable identifiers, ownership and environment fields, with a worked cross-system record example.
Published Updated
Published by FxTrusts, a supplier of brokerage and prop firm technology. Prepared with AI-assisted research and drafting; reviewed against the cited public sources. Examples are illustrative. Product links describe our services.
Quick answer
A client profile, wallet and trading account are different records with different identifiers. Connect them through explicit ownership and mapping fields rather than names, email addresses or coincidentally matching account numbers. Include platform and environment scope when an external identifier is not globally unique.
Identify the entity represented by each record
A client profile represents the person or organization in the CRM. A wallet record tracks a defined ledger or currency balance. A trading account belongs to a platform and account model. One client can have several wallets and several trading accounts. Product documentation such as UpTrader and B2CORE describes these operational categories, but the exact data model must be confirmed for the system being integrated.
Use stable keys and scoped external references
Display names and email addresses can change and should not be the only join keys. Preserve the CRM’s stable identifier and the platform’s external identifier, together with the environment, server or namespace needed to make the latter unambiguous. A demo account numbered 12345 and a live account numbered 12345 must not be assumed to be the same record. Record identifier provenance and avoid reusing retired IDs for new entities.
Keep ownership distinct from permission
A foreign-key relationship saying that a wallet belongs to a client does not by itself authorize every staff user to view or change it. Access checks need the actor, action and resource relationship. OWASP recommends enforcing authorization for each request and applying least privilege. That principle is especially relevant when a support agent can search accounts across brands or when an API accepts a client-supplied account identifier.
Make mappings reviewable during change
Provisioning, migration, account replacement and closure can all change the set of linked records. Retain effective dates and the reason for a mapping change rather than overwriting the only trace of the previous relationship. A failed mapping should be visible as an unresolved operation, not silently attached to the nearest matching email address. Reconciliation should verify uniqueness, ownership and referential integrity before financial events are associated with the destination account.
A fictional client with two distinct trading accounts
The identifiers below are invented and contain no customer data. Client C-104 owns one USD wallet and two trading accounts in different environments. The external account number happens to be the same, which is safe only if the mapping retains the environment and platform scope. No balance is inferred from the existence of the wallet record.
| Record type | Internal ID | External/scope reference | Owner |
|---|---|---|---|
| Client profile | C-104 | CRM production | Applicant entity |
| USD wallet | W-220 | Ledger production; USD | C-104 |
| Trading account | T-501 | Platform A; demo; 12345 | C-104 |
| Trading account | T-502 | Platform A; live; 12345 | C-104 |
Implementation checklist
- Define each record type and its stable internal identifier.
- Scope external IDs by platform, environment and server where required.
- Validate ownership separately from the current user’s permission.
- Retain effective mappings and reconcile them before attaching financial events.
Sources
These documents support the reference. Check the original publication for current requirements and the limits of its scope.
- UpTrader back-office workflowsuptrader.io
- B2CORE trader-room documentation and featuresb2broker.com
- OWASP authorization guidancecheatsheetseries.owasp.org
Continue with the broader guides
Connect this reference to platform selection and the wider operating workflow.