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

# Consumer Payment Review

> Jane's installment was sent to USAePay, but the gateway never confirmed what happened.

## Real-World Example

Jane's \$50 installment was sent to USAePay at 19:00, and the request timed out. Reconciliation looks the charge up by its saved reference, but USAePay still has no record of it a day later. The platform cannot tell whether Jane paid, so the payment moves to **review**. It stays there until the gateway answers or a person checks it.

A payment in review is still looked up once a day until 30 days after it was made. If the gateway later approves or declines it, the payment settles on its own: approved payments are recorded once, and declined ones go through normal failed-payment handling.

## What Goes to Review

| Payment | Goes to review when |
| - | - |
| Scheduled installment, Pay Now, partial, extra, or Pay Remaining Balance | The gateway still cannot find the charge, or gives an unclear answer, 24 hours after it was made. |
| Helping Hand gift | The gateway cannot confirm it within 24 hours, or a bank gift is still pending after 7 days. |
| Any of the above | The gateway holds the charge for its own review, such as a fraud review. |

Bank (ACH) payments that settle and are later returned by the bank do **not** go to review. They are reversed automatically. See [Installment Payment Processing](https://docs.younegotiate.com/portals/consumer/background-processing/installment-payment-processing.md).

## Visual Flow

```mermaid placement="top-right" actions={true} theme={"system"}
flowchart TD
    A["Charge sent, answer lost or unclear"] --> B["Reconciliation looks it up by reference"]
    B --> C{"Confirmed within 24 hours?"}
    C -->|Yes| D["Recorded as paid or failed"]
    C -->|No| E["Payment moves to review"]
    E --> F["Looked up once a day for 30 days"]
    F --> G{"Gateway answers?"}
    G -->|Approved or declined| D
    G -->|Still no answer after 30 days| H["Stays in review for a person"]
    I["Support or Claude checks the review list"] --> E
    classDef default fill:#F8FAFC,stroke:#64748B,stroke-width:1.5px,color:#0F172A;
    classDef actor fill:#E0F2FE,stroke:#0284C7,stroke-width:2px,color:#0C4A6E;
    classDef system fill:#F8FAFC,stroke:#64748B,stroke-width:1.5px,color:#0F172A;
    classDef decision fill:#FEF3C7,stroke:#D97706,stroke-width:2px,color:#78350F;
    classDef risk fill:#FEE2E2,stroke:#DC2626,stroke-width:2px,color:#7F1D1D;
    classDef outcome fill:#DCFCE7,stroke:#16A34A,stroke-width:2px,color:#14532D;
    class I actor;
    class A,B,F system;
    class C,G decision;
    class E,H risk;
    class D outcome;
    linkStyle default stroke:#94A3B8,stroke-width:2px;
```

## Finding Payments in Review

> [tab] Claude (Hub MCP)
>
> Hub integrations with read access have two read-only tools:
>
> * `search_payments_needing_review` lists every payment in review, oldest first. Filter by `type` (`scheduled_payment`, `manual_payment`, `helping_hand`) or `gateway` (`authorize`, `usaepay`).
> * `get_payment_review` shows one payment: amount, gateway and reference, why it is in review, how many lookups have run, and whether it is still checked daily.
>
> Example: *"Which consumer payments need review, and how long have they been waiting?"*

> [tab] Command line
>
> Support can look up one payment by its reference (`yn...`) or payment ID:
>
> ```bash theme={"system"}
> php artisan payments:lookup yn4Fq2...
> ```
>
> It shows the platform's record, then asks the gateway live and shows what it reports now. Add `--no-gateway` to show only the platform's record. The command never changes the payment.

## How It Should Work

* It should move a payment to review only after reconciliation could not confirm it automatically.
* It should keep looking up a payment in review once a day until 30 days after it was made, and settle it as soon as the gateway approves or declines it.
* It should keep the consumer's installments held while a payment is in review, so the same installment is never charged twice.
* It should list scheduled, manual, and Helping Hand payments in review together, oldest first, with the gateway reference support needs to look them up.
* It should keep lookups read-only: listing or looking up a payment never changes it.

## How It Should Not Work

* It should not send a payment to review when the gateway has given a clear approval or decline.
* It should not keep looking up a payment in review every few minutes.
* It should not show card numbers, bank account numbers, or payment tokens in the review list or lookup output.
* It should not email Super Admins about payments in review. Support finds them through the review tools.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.