MarketPlaces profile
MarketPlaces for DayTraders
MarketPlaces for Private Banking
MarketPlaces Commodities
Executive summary
Contact addresses and location
web links

MarketPlaces for Private Banking

By combining a number of MarketPlaces modules it is possible to create an integrated system for private banking. MarketPlaces philosophy entails that no two companies are completely alike. Therefore, catering to specific needs of a company can never be achieved using ‘of-the-shelf’ software solutions. The existing MarketPlaces modules enable us to create a tailor-made solution in a short period of time. Every customer has specific needs and demands. Therefore, every MarketPlaces project entails a percentage of tailor-made software development. A MarketPlaces implementation could look as follows:

MarketPlaces helps organizations to adapt to the ever-growing need for global investing. Through the Internet, MarketPlaces offers authorized persons (be it customers or staff) a complete order book. This (personal) order book enables swift and efficient order entry. One or more orders can be routed, through a trading desk or directly, to a number of exchanges. Local rules are checked whenever an order is generated, changed or deleted before the order is actually sent to the exchange of choice. For instance, MarketPlaces will generate a message if it is no longer possible to change an order because the order has already been executed.

Orders that do not go to the exchange directly are routed to the trading desk. The trader -or a team of traders- can forward the order to the exchange in one ore more market orders. The trader can also generate orders from the depth of the market. Order executions are automatically paired with client orders. It remains possible to process orders that have been entered using an ETW monitor.

MarketPlaces is built up out of different generic components that mirror the business of a brokerage firm. The flexibility, malleability and scalability of the order management system are greatly enhanced because of this component-based design. Because of the generic design it is possible to add new functionality and connections in a short period of time.

Authorization and user rights are managed using the components ‘authorization’ and ‘authenticity’. The ‘authenticity’ module manages the correct logging in and out procedures. The ‘authorization’ module manages the user rights. These user rights are implemented generically meaning that a highly detailed distribution of user rights is possible. It is also possible to match user rights with a maximum order value per specific client.

An application specific protocol coordinates the data exchanges between the different servers and between server and clients. The data sent will however be coded in XML.

Powered by Soops