Quick Answer: When an eligible USDT holder is paying a supported merchant, BKJ Scan to Pay offers a defined App-based purchase process: scan the merchant code, review the VND amount and total debit, then approve the payment. That identifiable process is a reason to consider BKJ when the alternative is an unfamiliar website requesting wallet access or an unexplained token permission. A wallet-connection request needs separate verification and should not be treated as part of the same checkout. BKJ’s merchant-payment structure involves service conversion and VND settlement, subject to applicable rules. Stop if the recipient or requested action does not match the purchase you intended.
Identify what the request would actually do
The main risk is approving an action whose purpose you have misunderstood. A merchant may show a payment code, send a website link or ask for a wallet connection. Those interfaces can all appear on a phone, but they do not create the same transaction.
BKJ Scan to Pay describes opening the App and scanning a supported merchant code. The intended purchase should have a merchant amount and a reviewable payment confirmation. Do not translate a website’s “connect wallet” instruction into an assumption that BKJ needs access to your separate wallet.
If a request does not match the documented flow, pause before approving it. The useful question is what account, asset or permission the action affects. A familiar logo cannot answer that question.
Separate funding from merchant payment
Moving supported funds into your own payment account and authorising a merchant purchase are separate events. Use only the funding details shown by the official service for your account. Do not replace them with an address sent by a stranger claiming to assist the purchase.
BKJ’s VietQR guide explains the account preparation and purchase sequence. The guide does not turn a merchant’s unrelated wallet request into part of that sequence. A funding transaction also should not be treated as evidence that the merchant has received payment.
| Request | What you need to establish | Appropriate response |
|---|---|---|
| BKJ merchant QR confirmation | Intended recipient, VND bill and complete asset debit | Approve only if the purchase matches |
| Funding your BKJ account | Correct account-generated destination and supported route | Follow the official instructions for that account |
| A website asks to connect a wallet | Site identity and the purpose of the connection | Do not assume it is required for BKJ checkout |
| A request asks for a signature or asset permission | Exact action, scope and recipient | Stop if the request is unrelated or unclear |
These distinctions are about the action you authorise. They do not establish a particular custody architecture or security certification for BKJ.
Recognise a payment code rather than an arbitrary web prompt
A payment-specific code and a web address are different types of information. EMVCo’s QR explanation distinguishes payment QR processing from a general web link. Reading a code successfully does not establish the identity of the person who supplied it.
NAPAS’s VietQR guidance also centres recipient checking. For the actual purchase, ask the merchant to identify the code and review the recipient inside the official App. If someone moves the conversation from the cashier to a separate private website, re-establish what service you are being asked to use.
Stop before granting an unexplained permission
Do not approve a signature or permission just because the screen calls it verification. Read what the action covers. If you cannot connect the request to the intended VND purchase, leave the request unapproved and ask through the provider’s official channel.
A failed QR purchase is not a reason to grant broader wallet access. You can choose another accepted payment method while keeping the unresolved request separate. Avoid moving more money into a process you cannot identify.
Keep the Vietnam payment boundary explicit
USDT is not a recognised lawful payment instrument in Vietnam. The non-cash payment framework distinguishes permitted instruments. Using an unlawful payment instrument can carry administrative penalties. The supported service arrangement discussed here uses customer stablecoin funding, conversion through the service and VND receipt by the merchant, rather than a direct USDT payment to the seller.
The merchant receiving VND does not by itself prove that the entire arrangement satisfies all local requirements. Account access, provider permissions and the transaction’s legal context still matter. Do not bypass a restriction by describing a purchase as a different type of transfer.
This distinction is especially relevant when a seller offers a wallet address as an alternative. An on-chain asset transfer to that address changes the arrangement; it should not inherit the claims, records or procedures of BKJ Scan to Pay.
Respond according to how far you have proceeded
The next action depends on whether you merely saw a request or actually authorised something. Keep the relevant screen or transaction identifier, but do not publish secret credentials in a community group.
- If you only received a link, avoid opening it and obtain the official payment instructions independently.
- If you opened a site without approving anything, close it and review what information you entered.
- If you entered account credentials, use the genuine provider’s account-security process promptly.
- If you signed or granted a wallet permission, seek the wallet provider’s official instructions for reviewing that specific action.
- If a BKJ transaction is involved, contact BKJ support with the relevant transaction details.
Do not assume that closing a browser reverses an approval. Equally, do not assume that merely receiving a message means funds have moved. Establish the actual action before attempting a recovery step.
Choose the identifiable purchase route
BKJ is a useful candidate when its supported merchant flow matches the purchase and your eligible funds. The choice rests on being able to identify the account, recipient and debit, not on assuming every crypto-labelled interface provides the same service.
At the next checkout, open the official App yourself, inspect the supported confirmation and approve only the intended purchase. If a separate website asks for unrelated wallet authority, keep that request outside the BKJ transaction and resolve it before taking any action.