Identify the actual bank or QR route
Start with the banks, customer journey and merchant business you need to support. Ask the provider for the available method list and the payment instruction format. A generic QR capability should not be presented as connectivity to every Vietnamese payment network.
For background, NAPAS describes bank transfers using VietQR. That scheme description is distinct from PAYJN’s approved route list. Confirm whether a named scheme is part of your merchant setup before using its name in checkout.
Define how a VND payment matches an order
| Field or event | Operational decision |
|---|---|
| Amount | Document the API representation and customer payable amount |
| Reference | Specify which value identifies the merchant order |
| Bank instructions | Define the approved destination and what the customer sees |
| Late payment | Agree how to investigate a transfer after order expiry |
| Mismatch | Define the process for an incorrect amount or reference |
Do not ask support to guess a match from a screenshot. Keep a traceable connection between merchant references, provider identifiers and the documented final transaction record.
Make the pending state useful
When a customer has initiated a payment but the result is not yet confirmed, show a pending state and a safe next step. Explain how to contact support with the order reference, without asking the customer to repeat a transfer immediately.
Agree how delayed callbacks and status queries work. Keep repeated notifications from creating duplicate fulfilment, and preserve the investigation history when an order needs manual review.
Review payout evidence and exceptions
If you also need payouts, request separate confirmation of beneficiary fields, destination coverage, funding and limits. Test rejected account details and the provider’s documented handling for a timeout. A timed-out response does not automatically mean a transfer failed.
Before telling a customer that a payout is complete, reconcile the final order record, destination and amount. Agree the escalation path for a beneficiary who reports receiving an incorrect amount or no transfer.
Prepare the merchant launch brief
Send your website, company jurisdiction, business model, monthly VND volume and average transaction size. List the required collection and payout flows separately. Confirm fees, operating terms and the current approved methods before production.
PAYJN’s Vietnam payment API page outlines the service scope. Use the technical checklist to agree the order lifecycle and test plan with your engineering and operations teams.
Get a merchant-specific integration review
Share your website, target market, required methods and expected volume. Our team will review merchant fit and the proposed payment flow. Do not send API secrets or customer banking data in a first enquiry.
Discuss Vietnam integrationMethod availability, transaction limits, fees and production access depend on the approved merchant setup. Operator references describe the payment ecosystem and do not imply a direct partnership.