> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/proprietary-fep-interface/reporting-proprietary-fep-interface/unconfirmed-transaction-report.md).

# Unconfirmed Transaction Report

The Unconfirmed Transaction Report displays all the declined and failed Store and Forward transactions. If a Store and Forward transaction is declined by the Host, it has to be manually settled.

This report also contains successful pre-authorized, but incomplete, transactions. This report accepts terminal batch numbers as input.

**Report Details:**

* **TITLE:** Unconfirmed Transaction Report.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/rVSHkIwjhl1bekSyCCWK/Unknown%20image)

* **DLR#:** Dealer identification number.
* **PRINTED:** Date and time the report printed.
  * **MM/DD/YY:** Date in month, date year format.
  * **HH:MM:SS:** Time in hour, minutes, and seconds.
* **WORKSTATION ID:** Workstation identification number.
* **TERMINAL BATCH:** Terminal batch number.
* **TERMINAL BATCH OPEN**: Time and date terminal batch was opened.
* **TERMINAL BATCH CLSE:** Time and date terminal batch was closed.
* **ACCOUNT NUMBER:** Account number for the proprietary card.
* **STAN:** System traced audit number (Transaction ID).
* **TOTAL AMOUNT:** Total amount of the card transaction.
* **TIMESTAMP:** Date and time of the transaction.
  * **MM/DD/YY:** Date in month, date year format.
  * **HH:MM:SS:** Time in hour, minutes, and seconds.
* **TRANSTYPE:** Proprietary card transaction detail.
* **TICKET#:** Receipt number.
* **PRODDESC CODE:** Description and code assigned to product.
* **QUANTITY:** Amount of transaction.
* **PPU:** Price per unit of transaction.
* **AMOUNT:** Amount of transaction.


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/proprietary-fep-interface/reporting-proprietary-fep-interface/unconfirmed-transaction-report.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.
