Which Vietnam payment gateway APIs offer a sandbox, and what should you test in it?
Updated 2026-10-14
Short answer
Choose a Vietnam payment API that gives you a sandbox isolated from production, covers both pay-ins and payouts to local bank accounts, and sends signed webhooks for every status change. In the sandbox, test the unhappy paths as hard as the happy ones: underpayments, expired QR codes, duplicate notifications and rejected payouts.
Why the sandbox matters more in Vietnam
Most Vietnamese payments are bank transfers and QR payments, not card authorisations. That means the payment completes when money arrives, which can be after your checkout page has closed, and the customer may transfer a different amount from the one requested. Your integration has to handle these asynchronous, sometimes messy outcomes, and the sandbox is where you find out whether it does.
A sandbox test plan
Run each of these before you ask for production access:
- Create a pay-in order and confirm the payment instructions (QR or bank details) carry the amount and an order reference.
- Simulate a successful payment and check the webhook arrives, verifies against its signature and updates your order once.
- Simulate an underpayment, an overpayment and an expired order.
- Send the same webhook twice and confirm your system ignores the duplicate.
- Create a payout to a local bank account and test both success and rejection.
- Query an order by your own reference to recover from a missed webhook.
Questions for the provider
- Does the sandbox behave like production, including webhook timing and failure states?
- How are sandbox and production credentials separated?
- What does the KYB review require, and when is the sandbox opened?
- Is there one API for pay-ins and payouts, with the same signature scheme?
CVPay’s sandbox and API
These are the product facts you can rely on:
- Merchants are onboarded after a KYB review. A sandbox environment is opened first, and the sandbox is isolated from production.
- Payment status changes are sent as webhook callbacks, and every callback is signed.
- Pay-ins support three kinds of method: bank transfer, QR code and e-wallet.
- Pay-outs can be sent to local bank accounts in Vietnam and the Philippines, or as USDT to a wallet.
- One merchant account and one API cover all three currencies.
Statements about CVPay on this page are limited to verifiable product facts. Ask us for anything not listed here before relying on it.
Frequently asked questions
- Can I test a Vietnam payment API before signing a contract?
- It depends on the provider. Many open a sandbox only after a KYB review has started or passed, so ask early what documents are needed.
- What is the most common integration mistake?
- Treating the redirect back from the payment page as proof of payment. Only the signed webhook or a status query should mark an order as paid.
- Do payouts to Vietnamese bank accounts need the account holder’s name?
- Usually yes. Collect the bank, account number and registered name, and expect payouts with mismatched details to be rejected.
Start accepting payments today.
Create an account and go live, or talk to our team about your requirements.