Our architecture is unique in supporting a complete split of retail and wholesale function, in a fashion analogous to the separation of retail and wholesale functionality in financial markets.
For example, in financial markets people never directly register with or are a direct customer of a particular stock exchange, be it the NYSE, NASDAQ or whichever. Rather they are customers of brokers (e.g., Schwab or e-trade) and it is the brokers who trade on the underlying exchanges on behalf of their customers. The broker provides retail function, including customer registration, payments to and from the customer, customer support and the acceptance of orders from customers. Brokers then interact with the trading platform, or "exchange," to provide wholesale function - i.e., trading, market making, liquidity provision, settlement and the enforcement of disclosure rules etc. A broker's customer's details are known only to the broker, and are not shared with the trading platform/exchange, or with any other brokers.
Our wagering technology architecture purposely mirrors this split in function so as to facilitate varied wagering options on a single platform, without the need to expose individual player identities/data to any third-party technology, tote, and ancillary services partners.
The system that manages customer data - the Broker-Engine - does not directly implement tote betting or any other form of betting for that matter. Rather the Broker-Engine manages all aspects of the customer - customer registration and logon, payments, CRM, acceptance of betting instructions from customers etc., and it is the Broker-Engine that interacts with other systems to execute betting activity. The Broker-Engine interacts with an underlying tote system for tote betting, with our Exchange-Engine for exchange betting and with external games or poker systems for games and poker.
A single Broker-Engine can support any number of Tracks/Operator Companies with each using the Broker-Engine to conduct their wagering businesses. This is a useful attribute as it enables a single Operator that has invested in its own instance of a Broker-Engine to allow the use of that investment to support the business of other companies without those other companies having to invest in or support a Broker-Engine themselves, thereby yielding significant economies of scale.
The Broker-Engine also supports White-Labelling, where one company permits another to separately brand its entry point to the Broker-Engine. The difference between an Operator and a White-Label is that an Operator runs its business independently, has a direct contract with its customers and 'owns' its customers whereas a White-Label is - by agreement - a company permitted to offer its customers access to the Operator's Broker-Engine through a separately branded portal, but without that company being directly involved with the operation of the business concerned.
The Broker-Engine is flexible and can be configured to support tote or exchange wagering, or both simultaneously. More than one Broker-Engine can forward bets to the same tote or Exchange-Engine.
