> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/access/local-governance-stack/trade-license-tl/tl-user-manual/citizen-user-manual/view-application-status-and-pay.md).

# View Application Status & Pay

My Applications option allows applicants to view their applications and track their status.

| <img src="https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/mO8pk0Idwvvz6Wy9pSyT/image.png" alt="" data-size="original">                                                              | <img src="https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/2txyBVrPK9rdh0EEgVTh/image.png" alt="" data-size="original">                  |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Click on **My Applications**.                                                                                                                                                                      | The screen displays all the applications tagged to the registered mobile number. Click on the **View Details** button to view the application details. |
| <img src="https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/mJ8NElzKvZoTmdVqmubE/image.png" alt="" data-size="original">                                                              | <img src="https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/pco1eKaHL4gCjrlWgh07/image.png" alt="" data-size="original">                  |
| The **Application Timeline** displays the selected application's current status and completed actions. For applications pending payment, click on the **Make Payment** button to make the payment. | Select the applicable **Payment Method** and click on the **Pay** button.                                                                              |
| <img src="https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/ONcrM9fESdXSnYtz6KnI/image.png" alt="" data-size="original">                                                              |                                                                                                                                                        |
| Click on the **Receipt** or **Certificate** button to download the receipt or the processed trade license certificate. Else, click on the **Go Back To Home** button to go back to the home page.  |                                                                                                                                                        |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/local-governance/access/local-governance-stack/trade-license-tl/tl-user-manual/citizen-user-manual/view-application-status-and-pay.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.