Overview
The Suspect Batches feature allows partners to review batch submissions that have ambiguous or inconsistent processing states. These batches may require further investigation or manual settlement due to discrepancies in terminal reports, processor acknowledgments, or auto-settlement settings.
This tool helps identify potential settlement failures before they result in missed payments or duplicate submissions.
Important: This document is for partners only. Merchants must refer to the Transaction Manager user guide for merchants.
Prerequisites
- You must have access to Transaction Manager with valid login credentials.
- If you do not have login credentials for Transaction Manager, please email the support team
support@chargeanywhere.comto request access.
Login URL
- Test URL:
https://sandbox.chargeanywhere.com/TransactionManager/Login.aspx - Production URL:
https://www.chargeanywhere.com/transactionmanager/login.aspx
Accessing Suspect Batches
- Log in to Transaction Manager with your partner credentials.
- From the top navigation bar, click the Tools tab.
- Select Suspect Batches from the dropdown list.

Results Table
Once loaded, the screen displays a table with all batches flagged as “suspect.” The following columns are visible:
| Field | Description |
|---|---|
| Channel | The channel from which the batch originated. |
| Processor | The payment processor (e.g., TSYS, Euronet) responsible for handling the batch. |
| Merchant Name | Name of the merchant whose batch is flagged. |
| Identification | Device or terminal ID associated with the batch. |
| Settlement Method | Method configured for settling the batch (e.g., Manual, Auto). |
| AutoSettle | Indicates whether the merchant’s account is set to automatically settle batches. |

Closing a Batch
To close a batch, perform the following steps:
- On the Suspect Batches page, locate the batch you prefer to close.
- Click the Close Batch link next to the corresponding row.

Use Case
Suspect batches typically appear due to:
- A mismatch between expected and actual batch totals.
- A batch not settled on time by the auto-settlement process.
- Network errors resulting in incomplete acknowledgments from the processor.
Action Recommendations
While no direct actions (for example, resubmit, delete) are provided on this screen, partners are advised to:
- Review each entry carefully for inconsistencies.
- Use the Identification and Processor data to trace settlement logs.
- Coordinate with the merchant or Charge Anywhere support if manual settlement or correction is required.