Short answer: Asian markets are wallet-fragmented rather than card-led. Japan alone has six or more meaningful consumer wallets, and Korea has a similar spread. India runs largely on UPI, which is a bank rail rather than a card. So a card-only Dynamics 365 checkout under-performs badly across the region. A payment connector adds these methods through one integration instead of one per market.

Western merchants consistently underestimate this. Therefore it is worth going market by market.

Why Asia breaks the card assumption

In much of Europe and North America, a card covers most consumers. Asia never consolidated that way.

Instead, each market developed its own dominant rails. Some grew out of messaging apps. Some came from retail groups or telecoms. Others, like India’s UPI, came from national infrastructure. Consequently a shopper in Tokyo, Seoul or Jakarta often reaches for a wallet first and a card second, if at all.

That fragmentation is the whole problem. It is also why a connector approach matters more here than almost anywhere.

Market by market

India

UPI dominates Indian digital payments. It moves money between bank accounts instantly through a simple identifier, and it costs far less to run than card acceptance. However, it is not a card, so no card gateway reaches it.

Japan

Japan is the clearest example of wallet fragmentation. Several wallets each hold large user bases, and shoppers are loyal to the one tied to their carrier, retailer or messaging app. Meanwhile Konbini payment remains genuinely important: customers pay in cash at a convenience store against an online order.

South Korea

Korea follows a similar pattern. Kakao Pay and Naver Pay sit on top of platforms Koreans already use daily, so adoption is high and habitual.

China

Two wallets carry the overwhelming majority of consumer payments. Therefore selling to Chinese consumers without them is close to pointless.

Southeast Asia

QRIS and PromptPay are national QR standards, so they reach far beyond any single wallet’s user base. Touch ‘n Go and DuitNow play comparable roles in Malaysia.

Australia

Australia’s New Payments Platform provides real-time account-to-account transfer alongside conventional card acceptance.

What this means for a Dynamics 365 merchant

Suppose you sell into Japan, Korea and Indonesia. Natively, that could mean three PSP relationships, three integrations, three settlement formats and three reconciliation processes. Then each one needs maintaining.

Most teams therefore do the obvious thing. They launch with cards, watch conversion disappoint in each market, and postpone the fix.

How SensePass handles it

SensePass connects your existing Dynamics 365 environment to 112 payment methods and 50+ processors through a single integration. The Asian methods above are already included, alongside global wallets such as Apple Pay, Google Pay and Samsung Pay.

Enabling a market is configuration. You integrate Dynamics 365 once. After that, adding PayPay or QRIS is a settings change. Nothing changes inside Business Central, Finance & Operations, or Commerce.

One connector, every region. The same integration also covers Brazil, Mexico and the wider Latin American markets. So a global rollout stops being a series of country projects.

Reconciled centrally. Every method posts back into Dynamics 365 automatically. Consequently your finance team works from one ledger rather than a settlement feed per country. For multi-entity and multi-currency structures, see Finance & Operations payments.

Physical retail included. With tap-and-pay, a customer taps their phone at the register and pays with their local wallet. There is no app download and no dedicated terminal.

Practical notes

Pick the top two or three per market. Full coverage on day one is unnecessary. However, missing the dominant wallet is fatal to conversion.

Konbini changes order timing. Like Latin American vouchers, convenience-store payment happens after checkout. Therefore you need an “awaiting payment” status and an expiry rule. See cash and voucher payments.

Watch currency and settlement timing. Use the transaction-date rate for the sale and the settlement-date rate for the payout, then post the difference to realised gain or loss.

Report by tender and market. Preferences shift quickly in these markets, so review the data rather than trusting last year’s assumption.

Frequently asked questions

Can Dynamics 365 accept UPI payments? Not through native card connectors. UPI is an instant bank rail, so it requires a local integration or a payment connector such as SensePass that already supports it.

Which wallets matter most in Japan? PayPay, Rakuten Pay, au PAY, d Barai, Merpay and LINE Pay all hold meaningful share. Konbini cash payment also remains widely used.

What are Kakao Pay and Naver Pay? They are the dominant Korean wallets, built on platforms Koreans already use every day. Adoption is high and habitual.

Do I need Alipay and WeChat Pay for Chinese customers? Effectively yes. Together they carry the large majority of Chinese consumer payments.

What is QRIS? QRIS is Indonesia’s national QR payment standard. Because it is a standard rather than a single wallet, it reaches a very broad user base.

Can one integration cover several Asian markets? Yes. Through a connector, each additional market is a configuration change rather than a separate PSP integration.

Will Asian methods reconcile in Dynamics 365? Yes. Transactions post back automatically, so you reconcile in one system rather than per country.

Sell in Asia the way Asia pays

The card assumption travels badly. In most Asian markets it costs you the majority of the addressable audience. One connector puts the local wallet, QR standard or bank rail in front of your customer — and still lands every transaction in Dynamics 365.

Request a demo, or read the Dynamics 365 payments overview.