> For the complete documentation index, see [llms.txt](https://docs.payshield.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payshield.ai/txalerts-dispute-alerts/appendix/status.md). # Status Status of the alert The status represents the current status of the alert.
StatusExplanation
RESOLVEDThe alert may have been resolved under many different conditions. the exact detail of the resolved alert can be sent via the reason_code parameter
DECLINEDThe alert may have been declined for many reasons. Details of the reason can be sent via the reason_code parameter
WIPThe merchant system may respond to an alert as WIP (Work-In-Progress). This will inform TxShield that the merchant system will need more time to respond. The reason_code parameter can hold the details.
RDR_DELETEWhen an RDR Delete is received for an RDR alert
--- # 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.payshield.ai/txalerts-dispute-alerts/appendix/status.md?ask=&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.