> For the complete documentation index, see [llms.txt](https://piramal-swasthya.gitbook.io/uba/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://piramal-swasthya.gitbook.io/uba/toasters/provider-toaster/developer-guide/frontend-guide/benefits-provider-app-ui.md). # Benefits Provider App UI The **Benefits Provider App** is a frontend application for providers to manage benefit applications and verifications. It allows viewing benefits, handling applications, and processing document verifications. ### Key Features * **Benefits Overview:** Access benefits catalog from Strapi * **Application Management:** View and process applications * **Document Verification:** Review and verify submitted documents * **Application Actions:** Approve or reject applications * **Application Form URLs:** Generate and manage beneficiary form links ### Technical Stack * **Frontend:** React with TypeScript * **Build Tool:** Vite * **UI Components:** Custom components + Material UI * **State Management:** React Context * **API Integration:** Axios ### External Dependencies * **Authentication Service:** JWT-based authentication, role-based access, session management * **Provider Middleware:** API communication, data transformation, business logic * **Benefits API:** Application processing, document verification, status management * **Catalog Manager (Strapi):** Benefits catalog management, schema definition, content management * **Beckn Integration:** BAP integration and BPP communication ### System Architecture * **Authentication System:** Token management, session handling, user profiles * **Form Components:** Application forms with validation * **Provider Management:** User management, organization setup, service configuration * **Security Features:** HTTPS enforcement, JWT handling, input sanitization, XSS protection --- # 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://piramal-swasthya.gitbook.io/uba/toasters/provider-toaster/developer-guide/frontend-guide/benefits-provider-app-ui.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.