> For the complete documentation index, see [llms.txt](https://docs.xaman.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xaman.dev/concepts/payloads-sign-requests/status-updates.md). # Status updates ### Overview When users interact with payloads, Xumm provides real-time status updates and results (e.g., rejected, signed with signature). These updates allow you to make your application user interface reflect the status of the interaction with the user, and return sign request results to your application. ### Real-Time Status Updates * Keep track of user interactions with the payload. * Update the UI to reflect statuses like "opened" or "signed". * They provide status but not the final resolved data (for security reasons, resolved data like signatures can only be separately fetched from the Xumm platform). ### Websocket Usage * Receive real-time updates in your front-end and back-end. * **Frontend**: Keep the user informed about the status. * **Backend**: Determine when you can fetch final results. * This ensures responsiveness and keeps the end-user informed. ### Fetching End Results * **Webhook**: Once the payload is resolved, a Webhook can be sent to your platform for backend processing. For more on WebHooks, see [Webhooks](/concepts/payloads-sign-requests/status-updates/webhooks.md). * **API/SDK**: Alternatively, fetch the payload end results using the Xumm API or SDK [https://github.com/XRPL-Labs/Developer-Help-Center/blob/main/js-ts-sdk/sdk-syntax/xumm.payload](https://github.com/XRPL-Labs/Developer-Help-Center/blob/main/js-ts-sdk/sdk-syntax/xumm.payload "mention") for more control and flexibility. ### Status Updates for End users Understanding the end user's workflow/experience is vital. The real-time status updates and Webhooks are not just technical tools but communication channels between your application and the user. By effectively using these features, you ensure an engaging and informed experience for the user. --- # 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://docs.xaman.dev/concepts/payloads-sign-requests/status-updates.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.