Local currency virtual accounts vs global named accounts: one gives you a local address, the other gives you a global one
If you sell to customers in Thailand, Vietnam and Australia, you have two broad ways to get paid. You can give each group of customers an account in their own country and currency, so they pay you with an everyday domestic transfer. Or you can give everyone one international account, based in a financial hub, that they pay by international wire. The first is a local currency virtual account. The second is a global named account. They solve different problems, and many growing businesses end up using both.
A local currency virtual account is an account number on a single country's domestic payment system, in that country's currency, opened in your business name. To a customer in that country, it is indistinguishable from the account of any local business. They pay it from their usual banking app, over the same rails they use to pay rent or a supplier.
Every market has its own rails. A few examples in Asia-Pacific and beyond:
| Market | Currency | Typical domestic rails |
|---|---|---|
| Thailand | THB | PromptPay and interbank transfer |
| South Korea | KRW | Interbank electronic transfer (KFTC network) |
| Vietnam | VND | NAPAS 247 |
| Indonesia | IDR | BI-FAST and bank virtual accounts |
| Philippines | PHP | InstaPay and PESONet |
| Singapore | SGD | FAST and PayNow |
| Hong Kong | HKD | FPS and CHATS |
| India | INR | UPI, IMPS and NEFT |
| Australia | AUD | NPP (PayID) and direct entry |
| UK | GBP | Faster Payments |
| Europe | EUR | SEPA credit transfer and SEPA Instant |
| United States | USD | Card and bank rails (ACH and wire) |
Why businesses use them. Customers trust and prefer paying locally, and they avoid international transfer fees and foreign-currency conversion on their side. Domestic transfers are usually faster and cheaper than international wires, and in many markets they are instant, around the clock. The account is in your name, so name checks pass and invoices look like those of a local supplier.
What they don't do. A local account is, by design, local. It typically receives only domestic transfers in its own currency, so an overseas customer who wants to send an international wire, or pay in a different currency, needs a different route. You also need a separate local account for each country.
A global named account is a multi-currency account, opened in your business name, held with a bank or licensed payment institution in an international financial centre. It is usually reachable over SWIFT, the messaging network banks use for international transfers, using a SWIFT/BIC code and an account number (or an IBAN in Europe). Because it can hold several currencies side by side, it acts as a central treasury: money arrives, is held in the currency it came in, and is converted or paid out as needed.
Many global accounts also come with "local details" in a few major currency zones, for example US dollar details that accept domestic US transfers, or sterling details that accept UK Faster Payments. Where offered, this blurs the line: a global account with local details behaves like a local account for those specific currencies.
Why businesses use them. One account can receive from payers in almost any country, without opening something new for every market. You can hold foreign currency instead of converting immediately, which helps manage exchange-rate timing. And it gives you a single hub from which to pay suppliers worldwide.
What they don't do as well. SWIFT payments can take from minutes to a few business days, and intermediary banks along the route can deduct fees, so the amount that arrives may be less than the amount sent. The payer usually bears the international transfer cost and their own bank's exchange rate. And with some providers, a "global account" is really a pooled account in the provider's name, with your name only in the payment reference, so check whose name the payer's bank will actually show.
Global accounts cluster in a handful of cities because that is where the world's currencies clear.
| Local currency virtual account | Global named account | |
|---|---|---|
| Currencies | One | Many |
| Payment rails | Domestic rails of one country | SWIFT, plus local details in some currency zones |
| Location | In the payer's country | In a financial hub (Hong Kong, London, New York, Singapore) |
| Who it serves best | Customers in that one country | Payers anywhere, especially where you have no local account |
| Speed for the payer | Often instant | Minutes to a few business days |
| Cost for the payer | A normal domestic transfer | International wire fees and possible intermediary deductions |
| Exchange rate | You control conversion after receipt | Often the payer's bank converts before sending |
| Name shown to payer | Your business name | Your name, if genuinely named; sometimes the provider's |
| What it gives you | Local presence | Global reach and a treasury hub |
A local virtual account gives you a commercial local presence. Your customers see a local account, in local currency, in your name. For many buyers, that is what "local" means.
It does not give you a legal local presence. You don't gain a registered company, a tax number, a business licence, or the right to employ staff in that country. If your activities there create tax or licensing obligations, a virtual account does not change them, and if you need a real local entity (for example to apply for investment promotion, sign local contracts or hire), you will still need to set one up. Treat a local account as the payment layer of your market entry, not the whole of it.
Most businesses that sell across several countries end up combining the two:
This gives customers the local experience they prefer while giving your finance team one place to see and manage everything.
DSGPay is built on the hub-and-spoke model:
All of it runs on the same accounts across DSGPay OneWeb, DSGPay DMA and the DSGPay GraphQL API. DSGPay is a licensed payment institution, not a bank; customer balances are not covered by deposit insurance schemes.