How to inspect a KHQR payment QR code
To inspect a KHQR payment QR code, scan an authorized test code or select its saved image in EMV QR Reader. Review the reported parsing results, merchant and currency fields, and raw payload. These checks help debugging; they do not establish that a bank accepted a payment or that funds arrived.
Use an authorized test example
Start with a code you are permitted to inspect and whose expected details you already know. A development or demonstration code is preferable to a customer’s live account information. Keep the original image so you can compare later observations with the same input.
The National Bank of Cambodia’s integration guide illustrates merchant-presented KHQR information and a separate payment flow. It is useful background for reading fields, but an older example document is not evidence that a particular app or integration meets every current scheme requirement.
Capture the payload in EMV QR Reader
EMV QR Reader accepts camera scanning and QR images from the photo library. Choose the input that matches what you have. For a printed code, keep the symbol visible and avoid a glare-obscured or cropped image. For an imported image, confirm that it contains the intended code.
The app also lists VIETQR, THAIQR and MPQR among its inspection formats. That scope does not mean every image is a supported payment payload. If the code cannot be parsed, preserve the error and input type rather than assuming the merchant account itself is invalid.
Compare fields with the expected test details
Review the merchant details, currency, additional data and static or dynamic information exposed by the parser. Compare each relevant value with your test fixture or the issuer’s expected data. A name that looks familiar is not independent evidence of the recipient’s identity.
Record the app’s reported mandatory-field and CRC-related results separately from what you personally checked. A checksum concerns the encoded data; it is not a bank approval. Do not treat a positive label, a present CRC field or a parsed payload as an exhaustive certification of scheme compliance.
- Confirm the input is the intended test QR.
- Read the parsed merchant and currency details.
- Record reported checks and any warnings separately.
- Compare the result with the authorized test fixture.
Keep a useful debugging record
The app can copy raw QR content for development and support. Include the app version, what you expected and which reported fields differ when creating an internal debugging note. Keep real account identifiers and payloads out of public issues or screenshots.
Actual payment status belongs to the relevant bank or payment system. Do not send money merely to prove that parsing succeeded, and do not use a screenshot of an inspector as a receipt. Use the record to reproduce a parsing question, and check settlement through the relevant payment system.
Questions
Does a valid-looking result confirm a payment?
No. Parsing and reported validation results are different from bank authorization or settlement confirmation.
Can I inspect a QR saved as an image?
The released app documents photo-library input as well as camera scanning.
Should I paste a customer’s raw payload into a public issue?
Use an authorized test fixture or an appropriately redacted internal report instead of exposing real account information.