The Complexities of Moving Money Through Emerging Markets

It's 7:30 AM in New York and you have six cross-border transfers to complete before the end of business. You start with the easy one.

USD to EUR, mid-six figures, client in Chicago paying a supplier in Frankfurt. Hit submit. SEPA Instant picks it up and the euros arrive in about ten seconds.

No early morning phone call with your counter-party, no chats on Signal, no human being necessary at any stage of the process. Done and dusted before the coffee's ready.

This is the way we want cross-border payments to work, and it’s the way it does work across much of the G7. It’s fast and automated, painless except in cases of severe market discontinuity.

Unfortunately, your business touches the rest of the world, where a tangle of disparate regulatory regimes makes each trade an exercise in patience. These are systems that support the economic livelihood of most of the world’s population, operating cross-border at speeds and at costs that belie their domestic sophistication. All because the rails that connect them were not designed for them. A world build for the G7 that no longer fits.

Back to the trades. One down, seven to go.

8:15 AM — São Paulo

USD to BRL.

You already know what's coming: a 3.5% haircut on arrival. Brazil's IOF,  a tax against every foreign exchange transaction, needs its cut. On your ten-million dollar transfer, that's $350,000 gone.

Your client calls you confused, she thought the IOF had been rescinded. She isn’t entirely wrong, that was the plan, but instead the government raised it in May, Congress repealed it, only for the Supreme Court to reinstate it again.

3.5%, nothing you can do.

If you were making this transfer inside Brazil, PIX would settle it in seconds, but you’re not. On a better day you might have made up some of the drag on the spread, but today one your best (and only) liquidity providers doesn’t want to deal with the risk so you’re forced to make other arrangements.

The funds will land tomorrow.

9:00 AM — Mumbai

A client's finance contact in Bangalore messages you: "Can you send this UPI?"

No. UPI requires an Indian bank account, which you do not have.

And anyway, cross-border UPI is designed for Indian travelers scanning QR codes at shops abroad, and is usually capped at about ₹1 lakh. Your client is trying to pay a software team six figures. UPI is out.

So you route through a licensed payment aggregator, one of fewer than twenty-five entities authorized to handle inbound cross-border flows under India's PA-CB framework. They handle the FEMA compliance, convert at a rate about 3% off mid-market, and deliver rupees to a bank account.

Your Bangalore contact receives the funds and moves them to UPI in two seconds.

10:30 AM — Nairobi

Aggregated remittance payments to Kenya.

You message your Kenyan banking partner on WhatsApp to coordinate the last mile. They reply fast: "M-Pesa or bank transfer?"

M-Pesa would be instant, 91% of Kenya uses it, and the system handles more transaction volume than the country's GDP.

But your rails don't connect to M-Pesa directly. Instead, the payment lands in a Kenyan bank account and your contact moves it to their mobile wallet themselves.

The real problem is what this corridor costs.

Sub-Saharan Africa runs 8.78% average remittance fees. If your client were using a traditional bank, they'd pay close to 15%. You're cheaper than that, but not much. Thin liquidity, multiple intermediaries – a perfect storm.

Your contact asks when intra-African transfers will get cheaper. You don't have a good answer.

You check the clock. It's almost noon. You've been putting off the hard ones.

12:30 PM — Dubai

You need AED delivered today.

UAEFTS operates 8 AM to 2 PM Gulf Standard Time, Saturday through Thursday.

In New York, that window is midnight to 6 AM. It opened while you were sleeping and closes in ninety minutes.

You message your UAE banking partner to rush the submission. They come back: "PoP code?"

Purpose of Payment.

Every inbound transfer requires one, give the wrong number and the transfer bounces. You pull up the invoice. Consulting fees. You send the services code. Your partner confirms and submits.

12:55 PM GST.

1:10 PM GST.

At 1:35 PM GST, twenty-five minutes before the window closes in Dubai you get a confirmation: settled.

If you'd missed it, the payment would hold until tomorrow morning in the Gulf. Tomorrow is Friday, UAEFTS is closed, which would mean that the earliest possible opportunity to complete the transaction would be Saturday.

2:00 PM — Shanghai

You saved the best for last.

Your client has a Chinese supplier. Getting money into or out of China means SAFE, the State Administration of Foreign Exchange, is involved in every decision.

Your Chinese banking contact sent you an updated compliance checklist this morning. It's longer than last quarter's. New identity verification requirements kicked in October 2025, record retention just went from five years to ten, and the documentation thresholds for your transaction type shifted in a recent circular.

You work your way through the checklist. Paperwork in order. You submit. You pray.

Your Shanghai partner confirms receipt, it will settle in one or two business days, which is fast by China standards. You've seen payments held for a week when documentation wasn’t perfect.

You have a colleague who handles nothing but China, you have no idea how they do it.

6:00 PM

Those six corridors weren’t special.

You could pick six different ones tomorrow: *Colombia, Egypt, Nigeria, Indonesia, Argentina, Singapore*, and hit six completely different walls.

Taxes and regulations, liquidity and risk – always something. Always changing. There are hundreds of these corridors, and none of them break quite the same way.

This is why major banking institutions never “fixed” the problem of cross-border payments, because it’s a thousand problems and the G7 pairs are profitable enough for the rest not to be worth the hassle.

To actually make rails that work for the rest of the world, for emerging markets and exotic corridors, you can't adapt a system designed to support EUR/USD and hope it travels. You have to build from the ground up, build with these complexities in mind.