> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/cug-57.02/commander-user-reference-57.02/store-and-forward-network-batch-monitoring.md).

# Store and Forward - Network Batch Monitoring

Store and forward Configure and monitor offline fallback transactions.

## Overview

Store and Forward manages fallback transactions when the payment host is unavailable.

Use it with your EPS and FEP configuration.

Host behavior can vary by processor.

{% hint style="info" %}
For CITGO sites, from Release 57.01, damaged batch settlement files are repaired automatically. See [Network Batch Monitoring](#network-batch-monitoring) below.
{% endhint %}

## Configuring Store and Forward

Configure Store and Forward in [Payment Controller](https://docs.verifone.com/cug-57.01-en/commander-user-reference-57.01/configuration-client-forms/payment-controller.md).

Go to **EPS Configuration** → **EPS Global Configuration** → **EPS** → **Misc**.

Review these fields:

* **Store and Forward Limit** — sets the number of fallback transactions allowed.
* **Online Velocity Check Required** — applies velocity checks to online and offline transactions.
* **Data Storage Time (In Days)** and related security fields — display retention settings.

EMV transactions can allow stand-in approvals when the host is offline.

Stand-in parameters are FEP-specific.

Refer to your FEP documentation before changing EMV stand-in values.

## Monitoring Store and Forward

Use [Tools](https://docs.verifone.com/cug-57.01-en/commander-user-reference-57.01/configuration-client-forms/tools.md) to review payment status.

Go to **Helpdesk Diagnostics** → **Payment Status**.

This view includes:

* Store and Forward count
* Current batch details
* Last transaction timing

### Network Batch Monitoring

Network Batch Monitoring protects CITGO sites from "stuck" network batches. It is available from Commander Release 57.01, and also in Commander Release 56.03 and Commander Release 55.02.

At the end of each network batch, the Commander saves the batch's settlement details in files and uses them to settle with the network. If the Commander lost power or restarted at the wrong moment, one of these files could be left empty or damaged. Store and Forward would then retry that batch again and again without any message, and the batches behind it could not settle either. Sites often found the problem only hours later.

#### What This Feature Does

Three layers of protection are applied to the network batch settlement process:

<table><thead><tr><th width="103" valign="top">Layer</th><th width="174" valign="top">Name</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">1</td><td valign="top">Prevention</td><td valign="top">Settlement files are written in a crash-safe way. The Commander prepares the file first and then swaps it into place in one step, so a power loss or restart cannot leave a half-written or empty file. Leftover temporary files from an interrupted write are removed automatically when the Commander starts.</td></tr><tr><td valign="top">2</td><td valign="top">Self-Healing</td><td valign="top">If a damaged or empty settlement file is found, the Commander rebuilds the settlement information from the other records it holds and settles the batch, either with approval or through the out-of-balance path. The batches behind it are no longer blocked. A rebuilt batch configuration holds the essential settlement fields only, which is enough for settlement to proceed.</td></tr><tr><td valign="top">3</td><td valign="top">Alarm</td><td valign="top">If automatic rebuilding fails, the alarm "BATCH CLOSE ERROR — CALL HELPDESK" appears on the POS alarm screen, in English or Spanish, so staff are told immediately instead of the system being silently stuck.</td></tr></tbody></table>

#### What Site Staff Need to Do

Nothing, in almost all cases. The protection is automatic and always on.

If the alarm "BATCH CLOSE ERROR — CALL HELPDESK" appears, call the Help Desk. The Commander could not repair the batch on its own, and settlement for that batch waits until it is recovered. This needs several files to be damaged at once and is very rare.

A recovered batch may settle through the out-of-balance path, so managers should keep reviewing settlement reports as part of their normal reconciliation routine.

#### Scope and Applicability

<table><thead><tr><th width="186" valign="top">Attribute</th><th valign="top">Value</th></tr></thead><tbody><tr><td valign="top">Network</td><td valign="top">NTS (CITGO brand only)</td></tr><tr><td valign="top">Transaction Types</td><td valign="top">All transaction types using NTS batch settlement</td></tr><tr><td valign="top">New Alarm</td><td valign="top">BATCH CLOSE ERROR — CALL HELPDESK (English and Spanish)</td></tr></tbody></table>

This feature is not active for non-CITGO brands. It applies only when the NTS network is installed. Reporting the status of CITGO network batches to the Verifone cloud health and alert system is not part of this feature.

#### Troubleshooting Network Batch Monitoring

**Settlement is stuck or batches are not settling**

Check the POS alarm screen for the "BATCH CLOSE ERROR — CALL HELPDESK" alarm. If it appears, or if batches are still not settling and there is no alarm, call the Help Desk.

**The feature does not seem active on a CITGO site after an upgrade**

* Confirm the site uses the NTS network (CITGO brand).
* Confirm the Commander software is Commander Release 57.01, Commander Release 56.03 or Commander Release 55.02, or later.
* If both are correct, call the Help Desk.

## Related functions

Use [Methods of Payment](https://docs.verifone.com/cug-57.01-en/commander-user-reference-57.01/methods-of-payment.md) when you need manual recovery options.

**26 - Force Post** is used for transactions processed while the host was offline.

Use [Network Functions](https://docs.verifone.com/cug-57.01-en/commander-user-reference-57.01/network-functions.md) for related host and payment network workflows.

## Troubleshooting

**If Store and Forward counts increase unexpectedly, verify host connectivity first.**

**Then review EPS settings and FEP stand-in parameters.**

**If behavior differs by card type, confirm processor-specific rules with your FEP provider.**


---

# 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.verifone.com/cug-57.02/commander-user-reference-57.02/store-and-forward-network-batch-monitoring.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.
