You tap a card in Tokyo, and a few seconds later your phone shows a charge in Hong Kong dollars. It feels instant. But behind that beep, money crossed a border, changed currency, passed through a card scheme’s netting engine, and was screened by at least two compliance systems.
This post walks the actual route your payment takes — the correspondent banks, scheme settlement layer, and compliance gates that make cross-border cards more expensive and complex than domestic ones. If you want the authorization step first, read our breakdown of what happens when a card authorizes.
Authorization and settlement are not the same trip
When you tap abroad, the terminal asks your issuer, through the card network, whether it can honor the charge. The issuer checks your balance, risk rules, and available credit, then says yes or no. That round trip is measured in seconds.
But no money moves during authorization. It is only a promise. The real movement — the funds flow — happens later, in batches, usually the next business day. The network nets transactions between banks and triggers settlement through pre-funded accounts. The merchant is not paid by the beep; the beep only starts the clock.
The correspondent banking step
Cross-border means at least two countries and usually two currencies. Your issuer cannot simply send yen to a Japanese merchant. Instead, it holds foreign currency at another bank inside the merchant’s country or currency zone. That is correspondent banking: Bank A keeps an account at Bank B so Bank A can make and receive payments in Bank B’s currency and jurisdiction.
In practice, your issuer maintains balances in the network’s settlement currencies — often USD or EUR — with correspondent banks. On settlement day, it sends those pre-funded dollars or euros into the scheme’s settlement account; the scheme distributes them to the acquirer, which credits the merchant. Your account is billed in HKD, but the issuer had to deliver USD to settle.
This is why a “yen” purchase can involve two conversions: yen to the scheme’s settlement currency, then to your home currency. The final HKD amount already includes the cost and markup of that plumbing.
If you are comparing how different cards price this, our fee calculator lets you model the FX and cross-border fees side by side.
Prefunding, positions, and FX risk
Because settlement happens later and in batches, the issuer cannot wait until the charge posts to find the foreign currency. It must prefund its settlement position — keep enough USD, EUR, or other settlement currencies on hand to cover expected net outflows.
That creates FX exposure. Between the tap and settlement, exchange rates can move. If the settlement currency strengthens, the issuer needs more HKD to buy the same amount of USD — a real cost, and one reason cross-border transactions carry higher fees or spreads.
Issuers manage this in two broad ways:
- Natural hedging: matching inflows and outflows in the same currency so they offset each other.
- Financial hedging: using FX forwards or swaps to lock in rates for the leftover net exposure.
Hedging is not about betting on currency markets; it is about removing an uncontrollable variable from the issuer’s profit and loss. Better forecasting means less spread for you.
When choosing a card, the issuer’s hedging and prefunding discipline matters more than the app icon. Our card comparison tool captures the cross-border fee and settlement variables that determine your real cost.
Compliance checks multiply across borders
Cross-border payments attract more compliance attention because more jurisdictions are involved. A single tap can touch the cardholder’s country, the merchant’s country, the issuer’s home country, the scheme’s location, and the correspondent bank’s jurisdiction.
The main checks are:
- AML and sanctions screening: transactions are screened against sanctions lists and suspicious-activity patterns. A hit anywhere in the chain can block the payment.
- FX controls and purpose declarations: some countries limit how much residents can convert or send abroad, and may require proof of what the payment is for. The same card can behave differently depending on where it is issued.
- Data localization: some markets require cardholder data to stay inside the country, shaping where servers and records must live.
This is why a cross-border decline is not always about your balance. Sometimes a party in the chain matched a sanctions list, or the transaction type is not permitted under local FX rules. For a broader view, see our regulations wiki.
What this means if you use a crypto or stablecoin card
Stablecoin-funded cards run on the same card-network rails. When you tap, the merchant, acquirer, and network still see an ordinary prepaid or debit card; the blockchain layer sits behind the issuer’s conversion engine.
That means all of the above still applies: prefunding, correspondent banking, scheme settlement, FX exposure, and compliance screening. If you top up in USDT but spend in yen, someone still has to bridge those currencies on settlement day.
The best card is not always the one with the lowest top-up fee. It is the one whose settlement timing, hold policy, FX markup, and compliance footprint fit how you actually spend. Our U Card guide covers the landscape of stablecoin cards and what to look for.
The short version
- Authorization is the information trip; settlement is the money trip, and it happens later in batches.
- Cross-border settlement runs through correspondent banks and a scheme’s netting engine, often in USD or EUR, even when neither side uses those currencies.
- Issuers must prefund foreign-currency positions and manage FX exposure; that cost flows back to you as fees or spread.
- Compliance checks intensify across borders: sanctions, AML, FX controls, and data-localization rules add friction.
- Crypto cards use the same rails; the stablecoin part is behind the scenes, but the cross-border plumbing still determines what you pay.
The next time your foreign charge differs from expectations, remember: the tap was just the message. The money took a longer trip.