Choose and Document the Product Model
“Stock trading” can describe cash equities, stock CFDs, fractional interests or another synthetic product. Those models differ in ownership, custody, settlement, market access, short selling, voting, dividends, disclosures and client-asset treatment. Confirm the legal perimeter before selecting software or publishing an instrument list.
The signed proposal should identify the product, contracting entities and providers. It should also state whether FxTrusts is configuring platform access, integrating a data or execution provider, coordinating operations or delivering another named service. Technology delivery does not create exchange membership, data rights, custody permissions or regulatory authorization.
Symbols, Reference Data and Market-Data Rights
Use the provider’s current symbol and entitlement files as controlled inputs. For each instrument, record the exchange or reference venue, identifier, client label, platform symbol, provider symbol, currency, price precision, contract size, volume rules, sessions, holidays and current status. Keep delisted, suspended and close-only states synchronized across the platform and client channels.
Real-time, delayed, derived, display and non-display data can have different licences and fees. Document who supplies the feed, which users and applications may consume it, whether redistribution is allowed, how usage is reported and what happens when an entitlement ends. A market-data connection does not itself establish execution access.
Orders, Pricing and Execution
Specify supported order types, time-in-force values, minimum and maximum quantity, fractional precision, partial fills, rejects, cancels, price bands and venue or counterparty identifiers. Test the exact interface and symbol group intended for production. A displayed quote is not a guaranteed fill, particularly around openings, halts, news and less-liquid instruments.
For CFDs, define the price source, spread or commission, financing, currency conversion and provider route. For cash equities, define the broker, venue, custody and settlement chain. Reconcile every order and position across the client platform, execution record, provider statement and financial ledger using stable identifiers.
Trading Sessions, Fractional Orders and Shorting
Main, pre-market and after-hours sessions can differ in liquidity, order types, reference prices and risk limits. Publish the actual provider-backed schedule and maintenance windows. Define behavior during auctions, halts, limit states, corporate events and session transitions.
Fractional and short orders need explicit support. Record how fractions are aggregated or executed, how rounding and residuals are treated, and whether clients hold a derivative or another interest. For short exposure, document provider availability, borrow or locate constraints where relevant, recall handling, close-only states and client disclosure.
Corporate Actions and Lifecycle Operations
Dividends, splits, reverse splits, rights issues, mergers, spin-offs, symbol changes, tender events, suspensions and delistings can affect positions and cash. Define the authoritative event source, supported event types, calculation, effective timestamp, rounding, tax or fee inputs, approval and client communication for the chosen product model.
Test representative events before launch and reconcile the resulting positions and cash. Keep a manual exception procedure for unsupported or late events. The provider contract and broker policy should control the final treatment; generic website wording should not replace them.
Broker Risk and Operating Controls
- Approve products, countries, client categories and marketing language through the legal perimeter.
- Set symbol, order, price, margin, exposure and concentration limits with named change authority.
- Monitor stale feeds, gaps, halts, rejected orders, unmatched positions and corporate-action exceptions.
- Restrict platform, provider and data credentials and record privileged production changes.
- Maintain daily order, position, cash, fee and event reconciliation with escalation owners.
Acceptance Evidence Before Go-Live
- Confirm the legal product model, client countries, provider contracts and market-data rights.
- Freeze and approve the versioned symbol, session and contract-specification files.
- Test normal and edge-case prices, orders, fills, rejects, cancels and currency conversion.
- Test halts, disconnects, recovery, fractional or short behavior and representative corporate actions.
- Reconcile client, platform, provider and ledger records and close material defects.
- Record named business, compliance, operations and technical sign-off.
Frequently Asked Questions
No. A stock CFD is a derivative contract that settles price differences under the broker’s product terms; it does not normally transfer ownership, voting rights or custody of the underlying share. Cash equities, CFDs, fractional interests and synthetic products require different contracts and operations.
The broker’s legal permissions, target-country rules, platform support and the contracted provider’s current symbol schedule control availability. Each live symbol needs an approved reference, currency, session, contract specification, data entitlement, margin rule and corporate-action process.
No. Fractional capability depends on the product model, provider, platform, order-handling process and legal terms. The proposal should state whether the client receives a CFD, beneficial interest, internal fraction or another instrument and how orders, custody and corporate actions work.
Only when the provider schedule, borrow or execution availability, platform rules and broker permissions support it. Sessions, close-only states, locate or borrow constraints, order types and risk limits should be specified per symbol or group.
The contract and symbol specification should define each supported event, source data, calculation, effective time, rounding, client treatment and reconciliation. A technology platform should not assume that every provider handles every event in the same way.
There is no universal timeline. The critical path depends on legal review, provider and data approvals, symbol files, execution access, corporate-action design, configuration, defects and acceptance testing. The signed implementation plan should name prerequisites and milestones.