„Retail Brokers On-Boarding Process” Alex Makhnitskyi, PFSOFT

PRESENTER 6 years experience in software development managing platform implementation managing on-boarding process Alex Makhnitskyi Head of Technical Support

India Ukraine China Poland Trading software developer Protrader multi-asset solution For banks and brokers In business since 2003 80 employees in 4 offices PFSOFT

Type of brokers

On-Boarding Process 1. Discuss deployment architecture 2. Server side deployment 3. System Configuration 4. Testing of failover & disaster recovery 5. Integrating with 3rd party systems 6. Front-End configuration, publishing (iOS/Android/Web/Win/Mac) 7. Testing application 8. Performance testing 9. Live Testing 10. Additional development

1. Deployment architecture

How many environments do we need? Live Demo UAT (Beta Testing) UAT (Production Acceptance Testing)

Do we really need 2 UAT environments? Software Provider does not have access to Production Environment Complicated structure of Production Environment Client does not «like» frequent updates

2. Server deployment

3. System configuration 1. Connection with Liquidity/Market Data/News providers 2. Trading Rules (Order Types, TIFs) 3. Instruments, Assets, Cross rates, Trading Sessions 4. Default User Group settings, Permissions 5. Commissions, Spreads, Swaps, Markups, Interest on Balance, Margin, Market Data Charging,... 6. Monitoring (hardware, app. services) 7. Emails, SMS and more..

4. Failover & Disaster Recovery Testing

5. Third Party Integration

6. Front-End configuration, publishing

7. Application testing

8. Performance Testing

Commission Settings 1 commission 5 commissions

Orders Execution Time

9. Live Testing

SUM UP Brokers do not have technical skills (usually) Consider proper number of environments Initial proper configuration is important Configuration affects performance Use technology for process automation Control on-boarding process

Questions? Thank you! I would be happy to answer your questions.