Zum Hauptinhalt springen
tsecurity.de LIVE
Echtzeit-Radar & Feeds
Alle RSS Feeds
👥 Community & Social
Windows Tipps & SecurityThe Blood of Dawnwalker Director Says 60 FPS Is Enough for This RPG(23.09.2026 um 14:37 Uhr)
Windows Tipps & SecurityMeyer Sound ernennt John McMahon zum Chief Operating Officer(23.09.2026 um 11:19 Uhr)
Windows Tipps & SecurityTouchscreen erweitert Grill-Sortiment am Point of Sale(23.09.2026 um 13:45 Uhr)
Windows Tipps & Security„When Worlds Unite“: ISE 2027 erweitert Messe und Programm(23.09.2026 um 13:45 Uhr)
Sichere ProgrammierungWhat Full-Stack AI Engineering Means in Real Projects(23.09.2026 um 14:00 Uhr)
Sichere ProgrammierungThe Internet Changes Everything (Slowly)(23.09.2026 um 14:09 Uhr)
Sichere ProgrammierungMAUI vs React Native vs Flutter vs Ionic(23.09.2026 um 14:09 Uhr)
Sichere ProgrammierungAI Tools Used in Modern Software Development(23.09.2026 um 14:22 Uhr)
Sichere ProgrammierungHealthAuditor — Website Health & SEO Audit Tool(23.09.2026 um 14:24 Uhr)
Windows Tipps & SecurityThe Blood of Dawnwalker Director Says 60 FPS Is Enough for This RPG(23.09.2026 um 14:37 Uhr)
Windows Tipps & SecurityMeyer Sound ernennt John McMahon zum Chief Operating Officer(23.09.2026 um 11:19 Uhr)
Windows Tipps & SecurityTouchscreen erweitert Grill-Sortiment am Point of Sale(23.09.2026 um 13:45 Uhr)
Windows Tipps & Security„When Worlds Unite“: ISE 2027 erweitert Messe und Programm(23.09.2026 um 13:45 Uhr)
Sichere ProgrammierungWhat Full-Stack AI Engineering Means in Real Projects(23.09.2026 um 14:00 Uhr)
Sichere ProgrammierungThe Internet Changes Everything (Slowly)(23.09.2026 um 14:09 Uhr)
Sichere ProgrammierungMAUI vs React Native vs Flutter vs Ionic(23.09.2026 um 14:09 Uhr)
Sichere ProgrammierungAI Tools Used in Modern Software Development(23.09.2026 um 14:22 Uhr)
Sichere ProgrammierungHealthAuditor — Website Health & SEO Audit Tool(23.09.2026 um 14:24 Uhr)
Intelligence View
⚡ tsecurity.de Intelligence

I quietly lost ~1.7% of a year's pay to transfer fees. Here's the full breakdown.

For the past year I worked on a remote contract with a US tech company. Paid in USD, ultimately needing Korean won. Simple, right? Then a year in, I actually reconciled what landed in my account. The exchange rate had gone up — and yet my …

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

For the past year I worked on a remote contract with a US tech company. Paid in USD, ultimately needing Korean won. Simple, right?



Then a year in, I actually reconciled what landed in my account. The exchange rate had gone up — and yet my real received amount was lower than I'd expected. I traced it, and money was leaking at every step of the transfer path I hadn't been watching.



This is what I learned switching routes over that year: from a direct bank wire to Wise, the real cost difference, and one right buried in my contract. If you're a freelancer or contractor in any country earning USD from abroad, this should save you something.






Money leaks in more than one place



Getting USD from overseas into local currency looks like one step. It's actually at least four:




  1. The wire fee from the US bank, through correspondent banks, to the receiving bank.

  2. The exchange rate the receiving bank applies — this is the big one.

  3. The receiving fee on the destination side.

  4. A hidden "lifting charge" some correspondent banks skim.



The largest is the rate. Banks quote two rates, and the "buyer rate" applied when an individual sells dollars is worse than the mid-market reference — typically a 1.5–2% spread. On $1,000, that's $15–20 gone to the rate alone.



That number looks small. Accumulated over a year, it stops looking small.






Route A — receiving directly through a major US bank



My first setup was the simplest: the company wired USD to my US bank account, and I wired it on to my Korean bank. I picked this at contract start without much thought, assuming the client would conventionally cover fees anyway. (Lesson one: specify the transfer method, route, and who pays in the contract.)



The problem was the bank's exchange rate. It applied the buyer rate straight up, with a wider-than-usual spread versus mid-market — plus a send fee, plus the Korean receiving bank's fee.



I only noticed months in. Comparing statements, there was a steady 2–3% gap between the won I'd expect at mid-market and the won that actually arrived. Per dollar, ~20–30 KRW. On a monthly contract amount, a meaningful sum was vanishing every single month — at the high end, over 300,000 KRW in a month.



The moment I realized 2–3% of my contract was a constant that disappeared whether I worked or not, I decided to change routes.






Route B — switching to Wise



I landed on Wise. It's the most-recommended option among Korean freelancers, minimizes the middle margin, and gives a rate close to actual mid-market.



The limit worry turned out to be a non-issue. Before switching, my biggest concern was Wise's annual receiving limit for personal accounts — there's a lot of "you'll need a business account" advice out there (I looked at OFX as a backup for this reason). In the end I finished the contract comfortably inside the personal limit. Monthly and annual caps both apply, but at my contract size there was room. Calculate your projected annual receipts first; if you're under the cap, there's no reason to jump to a business account.



The cost difference was obvious from month one. The spread versus mid-market dropped to less than half, and fixed fees are shown transparently — no "skimmed somewhere in a correspondent bank" black box.



Roughly:





  • Direct bank wire: ~2–3% loss vs. mid-market


  • Wise: ~0.7–1% loss vs. mid-market



Same contract amount, only the route changed, and the monthly received amount went up. Over several months that added up.






Putting a year in numbers



Comparing a full year on the bank route (hypothetical) vs. Wise (actual), ratios only:




  • Bank route: final received ≈ 2.5% under mid-market

  • Wise route: ≈ 0.8% under

  • Difference: ≈ 1.7 percentage points



Annualized, 1.7% of the contract total came down to route choice alone. Same work, same contract, one variable swapped. Small monthly, not small over a year.






The clause hiding in your contract



Here's the most important find.



Most remote contracts contain something like "payment to a bank account designated by the contractor." Read literally, that means the contractor can designate the method and route too — not just the account number.



I used the bank route early on simply because I set it up that way out of ignorance, not because the company required it. Mid-contract I requested a route change, and the company accepted with zero friction. The transfer route is the contractor's choice, not the company's prerogative.



Had I known this on day one, I'd have used Wise from the start. The cost of not knowing, over a year, was real.






Checklist — if you're in a similar spot





  • Decide the transfer route before you start. The company's default is its convenience, not your optimum. Direct wires from large US banks tend to be expensive.


  • Calculate projected annual receipts first. Under the personal cap? Skip the business account. Over it? Consider running OFX or similar in parallel.


  • Read the "designated account" clause carefully. In most standard contracts the route is your call, and asking to change it is no big deal for the company.


  • Reconcile every statement against mid-market. If the spread stays above ~2%, it's time to switch.



I hope this protects a few people's annual pay.






If you get paid across borders, what's your routing setup? Anyone found something cleaner than Wise for KRW (or your own currency)?

Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten I quietly lost ~1.7% of a year's pay to transfer fees. Here's the full breakdown.

Thematisch verwandte Begriffe: quietly, lost, years, transfer · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-95625 | The Tauri updater plugin verifies update binaries using minisign signatu…
Advisory →
TTS Reader • tsecurity.de Voice
tsecurity.de Icon
tsecurity.de App
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
🔖 Gespeicherte Artikel
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel Rechts: nächster Artikel unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...

Zurück: vorheriger Vor: nächster
↗ Original-Quelle
Social Reaktionen Deine Reaktion zählt
Einstufung & Relevanz-Poll 0 Stimmen
In sozialen Netzwerken teilen 1-Klick