eTrade

Challenge

A brokerage website has to do several awkward things at once. It must speak to visitors across very different markets, in languages that read in both directions. It must show market information and let visitors calculate margin, pip value and position size accurately, which means real numbers rather than illustrations. And it must do all of that while saying only what the business can actually support.

Solution

A fast, self-contained front end where language, prices and calculations are handled in one coherent layer rather than bolted together from separate widgets.

• Seven languages, with full right-to-left layout for Arabic and Urdu
• One price layer feeding the ticker, the quotes board and every calculator, so the same number appears everywhere
• Calculators that fill in a live price themselves instead of asking a visitor to type one
• Funding methods shown with clear availability states, so nothing unsupported is advertised
• Legal documents reachable and linkable without JavaScript
• Every account action routed to the client portal, with no customer data on the public site

Technology

Plain HTML5, CSS3 and JavaScript with no framework, which keeps the page fast and removes a whole class of dependency risk. Third-party analysis widgets provide the chart, technical gauge and economic calendar. Because those widgets sit in separate frames the page cannot read their numbers, so the calculators are driven by the site’s own price layer instead. That detail decided the architecture.

Implementation

The public site carries no CRM, no login, no payments and no customer records. Those already existed and stayed where they belong. Every action a visitor takes, from opening an account to funding it, hands over to the client portal through addresses held in configuration rather than written into the page.

Outcome

A live multi-language brokerage front end, with sTrader presented as the trading platform behind the brand. For Aim IT the project connects both halves of the company: financial technology on one side, and the front-end, infrastructure and integration engineering that makes it work on the other.