> ## Documentation Index
> Fetch the complete documentation index at: https://help-loyalife.xoxoday.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pending transactions

> Review, approve, or reject transactions flagged for review by Loyalife's Fraud Prevention module.

When a transaction exceeds a configured threshold, it is held in a pending state rather than being processed automatically. The Pending Transactions screen is where your team reviews these flagged items and decides whether to approve or reject them.

## Accessing pending transactions

Navigate to **Fraud Prevention → Pending Transactions**.

## What you see

Each pending transaction shows:

| Field            | Description                                       |
| ---------------- | ------------------------------------------------- |
| Transaction ID   | Loyalife's internal reference for the transaction |
| Member           | The member associated with the transaction        |
| Transaction type | Accrual or redemption                             |
| Points amount    | The number of points involved                     |
| Reason flagged   | The threshold that was exceeded                   |
| Submitted at     | When the transaction was received                 |

## Reviewing a transaction

For each flagged transaction, you can:

* **View details** — see the full transaction data, including the source reference and any metadata submitted with the transaction
* **View member profile** — check the member's history to assess whether the transaction looks consistent with their normal activity

## Approving a transaction

If the transaction appears legitimate, click **Approve**. The transaction is processed and points are credited or debited from the member's account.

## Rejecting a transaction

If the transaction appears fraudulent or erroneous, click **Reject**. The transaction is cancelled and no points are moved. The event is recorded in the audit trail.

<Info>
  When a pending transaction is rejected after points were already provisionally credited, the cancellation generates a **Debit By Cancellation** entry on the member's ledger, netting the balance back. If an approved transaction is later reversed by an admin, it appears as a **Debit By Reversal** entry. Both are filterable in Transactional reports under [Reports & Analytics → Transaction Category](/user-guides/reports/report-types#transaction-categories).
</Info>

<Tip>
  For systematic fraud patterns (e.g., a specific product code being exploited), update your [Threshold Settings](/fraud-prevention/threshold-settings) after rejecting the offending transactions to prevent recurrence.
</Tip>

## Audit trail

All approval and rejection actions are logged, including which administrator made the decision and when. This record is available in the [Administrative Data report](/reports/report-types).