What's Not Covered Yet: Merchant KHQR, Going Live, and Callbacks

Table of Contents

1. Why this chapter is short
2. Merchant KHQR and the endpoints beyond Individual KHQR
3. Going live and callback notifications
4. Beginner Pitfalls

---

1. Why this chapter is short

Every other chapter in this series is backed by code that was actually run against bakong-khqr and the production Bakong Open API. Merchant KHQR, batch status checks, deeplinks, business onboarding, and callback notifications weren't — they're genuinely unwritten parts of the source project this series is based on. Rather than guess at endpoint shapes or invent a callback mechanism that was never confirmed to exist, this chapter states plainly what's known to exist and what isn't.

2. Merchant KHQR and the endpoints beyond Individual KHQR

The official docs confirm these exist, but none are implemented in this series' example:

• Merchant KHQR (MerchantInfo + generateMerchant) — adds a Merchant ID and acquiring bank to the QR, for businesses rather than individual accounts, as opposed to the IndividualInfo + generateIndividual KHQR built in Part 2.
• Batch status checks (check_transaction_by_md5_list) — checking multiple transactions in one call, instead of Part 3's one-at-a-time check_transaction_by_md5.
• Deeplinks (generate_deeplink_by_qr) — generating a deeplink instead of, or alongside, the QR image this series renders with qrcode.
• Programmatic token renewal (renew_token) — this series renews the access token manually through the portal (Part 3); automating that via the API endpoint isn't covered.

3. Going live and callback notifications

• Business onboarding — how a business (rather than the individual Bakong account this series uses) is onboarded through a licensed bank/PSP. Unlike this site's ABA PayWay Tutorial, no firsthand experience with Bakong's onboarding process exists yet to write honestly about here — this will be added once it's actually been lived through, not guessed at.
• Callback/webhook notifications — unlike ABA PayWay's documented return_url callback, no equivalent server-to-server notification mechanism has been confirmed to exist for Bakong KHQR in the sources reviewed while writing this series. Polling (Part 3) is the only status-check mechanism implemented here.

If you're integrating for real, these are the next things to check, and the source repository is the place to look for whether any of this has been written up since.

4. Beginner Pitfalls

• Don't assume a callback mechanism exists for KHQR just because ABA PayWay has one — treat that as unconfirmed rather than assuming parity between the two integrations.
• Don't build a guessed renew_token API call or a guessed Merchant KHQR request shape — verify against the current Bakong Open API Document and KHQR SDK Document first, the same way every confirmed detail in this series was checked.
• Don't treat this chapter's silence on a go-live checklist as "there isn't one" — it means the process specifically hasn't been lived through yet for this series, not that it doesn't exist.