> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/interfaces/backoffice/transactions/declined-reservations.md). # Failed transactions Here you will find the failed transaction attempts.
You can adjust the view and the displayed columns on the right, next to the search. Available for display are: * Date * Source of Failure * Reason * Type * Amount * Reference number * Transaction ID * Payment means * Payment means details * Terminal At the top, you can search for a transaction by using the **Reference number/OrderId** that has been generated by your shop, and the Saferpay transaction ID. Below, you will find filters for date, currency, amount, provider, reference number and transaction ID ranges, source of failure, used terminal(s) and type of the transaction. ## Declined reservations details ![(click to enlarge)](https://3537448238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fzpi9teY7Tm2pCZ1Bw8zO%2Fuploads%2FKFuD9W79AIy6H4qXBGp1%2FBO_DeclinedTransactions_Details.png?alt=media\&token=2ee60354-093f-41e4-8830-e61a61944ff8) By clicking on Details for a given transaction, you can gather more information about the decline, like the full error, the amount, Saferpay **Transaction ID**, the order **description** as well as the masked **card number**, which can also be demasked, similar to the normal Journal. {% hint style="warning" icon="info" %} Remember that the demasking of PANs is deactivated by default and can only be activated account-wide for all logins. If you need this feature to be activated, please contact your account manager at [our sales.](/home/integration-guide/support.md#worldline-sales-team) {% endhint %} --- # 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.saferpay.com/home/interfaces/backoffice/transactions/declined-reservations.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.