> For the complete documentation index, see [llms.txt](https://dev.payon.com.kh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.payon.com.kh/how-to-implement/how-to-implement-qr-payment/web-base-implementation.md).

# Web Base Implementation

![Figure 01: Web Base QR Payment UI](/files/iujZf784LJ0kLksUQUYz)

### Description 

1. Customer who have the 3rd party account choose  3rd party as payment method.
2. PAYON's PG request initialize transaction to 3rd party and display KHQR on PAYON's PG page.
3. Customer open 3rd party apps to scan KHQR for payment.
4.  After customer scanned, PAYON's PG change screen to "KHQR Scanned Screen". [See More](/how-to-implement/how-to-implement-qr-payment/web-base-implementation/step-2-notify-qr-scan-screen.md)
5. After customer scanned, The 3rd party display transaction details to customer for confirm payment.
6. Customer will see transaction details on 3rd party app, and confirm for next step.
7. After customer confirmed, PAYON's PG will change screen to "Processing Payment Screen". [See More](/how-to-implement/how-to-implement-qr-payment/web-base-implementation/step-3-notify-processing-payment.md) 
8. Customer need to verify authentication base on 3rd party app (PIN, fingerPrint, faceID)
9. Display PAYON's PG result page 
10. Display 3rd party's result page on mobile app.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.payon.com.kh/how-to-implement/how-to-implement-qr-payment/web-base-implementation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.