> For the complete documentation index, see [llms.txt](https://developers.doku.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.doku.com/accept-payments/doku-checkout/additional-feature/promo-on-doku-checkout-page.md).
# Promo on DOKU Checkout Page
Applying a promo code during checkout allows customers to save on their purchases. Here's a **step-by-step guide** on how your customers can apply a promo code to their payment :
1. #### Setting up a Promo
Before applying a promo code, it first needs to be set up and configured. If you haven't done this yet, please refer to our guide on how to set up a promo [here](https://docs.doku.com/enhancements/promo-engine/set-up-a-promo).
2. **View Promo List**
To view the available promos, click on the **"See Promo"** button that is seen on the checkout page.
3. **Apply Promo**
To apply promo to checkout orders, customer must click "apply". The discount amount will be shown. Customers can proceed with the payment by entering their payment credentials, such as a credit card number or any other relevant information required for their chosen payment method.
4. **Complete the Payment**
Customer can finalize the payment and enjoy promo!!
---
# 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://developers.doku.com/accept-payments/doku-checkout/additional-feature/promo-on-doku-checkout-page.md?ask=&goal=
```
`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.