forex-scalping.com

The True Cost of Converting Local Currency to Dollars and Back

Scenario: you fund a dollar-denominated trading account from a country with a local currency, LCU. The mid-market rate is 1,500 LCU per dollar. Your payment provider converts at an effective 1,545 LCU per dollar for deposits, and 1,455 LCU per dollar for withdrawals.

Deposit. You send 1,500,000 LCU. At the mid-market rate, that would be 1,000 dollars. At 1,545, you receive 1,500,000 divided by 1,545, which is 970.87 dollars. The cost is 29.13 dollars, 2.9 percent.

Withdrawal. Suppose you withdraw the same 970.87 dollars. At the mid-market rate, that is 1,456,305 LCU. At 1,455, you receive 1,412,621 LCU. The cost is 43,684 LCU, 3.0 percent.

Round trip with no trading at all: you start with 1,500,000 LCU and end with 1,412,621, a loss of 87,379 LCU, or 5.8 percent.

So before your first trade, you need a gain of about 6.2 percent in dollars to break even in local currency. That is bigger than many monthly returns.

Compare with the trading edge of a typical strategy, and the importance of conversion cost becomes obvious. A trader who deposits and withdraws monthly pays far more than one who does so once a year.

Reducing it: compare providers, use larger and less frequent transfers, and check for peer-to-peer rates, with attention to scams.

Also record each rate, for your accounts and any reporting obligations.

Exercise: compute your round-trip cost using actual quotes from two providers.

The common assumption is that anything running in a browser must add delay compared with a desktop terminal. Sometimes that is true, but the reasoning behind it is usually off.

The order itself travels over the same kind of connection either way. A web platform typically talks to the broker through a persistent connection, so the network leg can be close to what a desktop client gets. What differs is everything around it: the browser has to run scripts, draw the chart, and share memory with every other tab. A browser with twenty tabs and a few extensions is a much noisier environment than a dedicated terminal.

That means the delay is often local and variable. It shows up as a pause when a tab has been in the background, since browsers throttle inactive tabs, and as dropped smoothness on a busy chart. A dedicated browser profile with nothing else open, kept in the foreground, can behave far closer to a desktop client than expected.

Still, a desktop terminal on a VPS removes the browser from the equation completely, which is why it stays the default for tight scalping.

Have you ever timed fills from a web platform against a desktop terminal on the same account, and what difference did you see?