ZaloPay for business: how to accept ZaloPay payments

ZaloPay and the Zalo ecosystem

ZaloPay is operated by a company in the VNG group, the same group behind Zalo. The wallet can be opened as a standalone app or from inside Zalo itself, and users link a Vietnamese bank account to fund payments. Because so much everyday conversation in Vietnam, including between shops and their customers, already happens in Zalo chats, ZaloPay often appears exactly where a sale is being agreed.

That makes ZaloPay particularly relevant for sellers who take orders through Zalo Official Accounts or mini apps, for services sold on mobile, and for audiences that already shop through chat. For a purely desktop audience it matters less, and VietQR usually does more of the work.

Is ZaloPay worth adding to your checkout?

Whichever answer applies, test with your own customers. The wallet that wins in one category of goods may be a minor option in another.

• Yes, if a meaningful part of your sales conversations already happens in Zalo, or if your users are young, mobile-first and wallet-heavy.
• Yes, as a second or third wallet next to VietQR and MoMo, so customers who keep their balance in ZaloPay are not pushed to another method.
• Less urgent if your customers are mostly businesses paying by bank transfer, or if you sell mainly on desktop.

Direct program or payment gateway

ZaloPay’s merchant program is built for businesses that are registered in Vietnam and settle to a Vietnamese bank account; its own business pages list the current requirements. If you are such a business and want only ZaloPay, applying directly can work.

A payment gateway that already supports ZaloPay is the more common route for foreign companies and for anyone who wants several methods at once. You deal with one contract and one company review, build against one API, and receive ZaloPay results in the same format as VietQR or MoMo. That matters more as order volume grows and reconciliation across several dashboards becomes a daily cost.

ZaloPay integration through CVPay

Each step pairs a fixed CVPay product fact with the work on your side.

1. 01

   Get reviewed, then build in the sandbox

   Merchants are onboarded after a KYB review. A sandbox environment is opened first, and the sandbox is isolated from production.

   Send the company documents and business description we ask for. In the sandbox, cover the paths customers actually take: paying from inside Zalo, cancelling halfway, and coming back after the order has expired.

2. 02

   Keep one code path

   One merchant account and one API cover all three currencies.

   Model ZaloPay as one value of a payment-method field, not a separate integration, so your order and refund logic is shared with your other methods.

3. 03

   Check what is enabled

   Pay-in methods include VietQR, MoMo, ZaloPay and Viettel Money in Vietnam, and GCash, Maya, GrabPay and QR Ph in the Philippines.

   Confirm with us that ZaloPay is active on your merchant account before you add the button, and remove any method from checkout that is not.

Practical notes for a ZaloPay checkout

• If you sell inside Zalo chats, send a payment link or code from your system rather than asking for a manual transfer, so every payment carries an order reference.
• Name the method “ZaloPay” with its logo; “e-wallet” alone gets fewer clicks.
• Mobile app switching is where payments get lost. Show a clear “waiting for payment” state and let the customer reopen the payment if they come back.
• Reconcile ZaloPay together with your other methods every day, by reference, not by amount.