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

# Review identity queue items

> Find customers and paykeys in review and collect the details needed for a decision.

Find customers and paykeys with a recorded status of `review`, then retrieve their review details. This workflow gives you the IDs and evidence to organize the next review action.

## Before you begin

* Install the [Straddle CLI](https://docs.straddle.com/developer-tools/cli/install.md) and configure an API key with access to the customers and paykeys you want to review.
* Confirm your [environment, integration type, and acting account](https://docs.straddle.com/developer-tools/cli/auth-context.md).
* Keep that context and database throughout. For a custom database, add the same `--db PATH` to every `sync` and `review-queue` command.

For marketplace integrations, customers and paykeys belong to the platform. These results cover platform-owned records. The selected acting account identifies the local database context used throughout this workflow.

## Run the workflow

**1. Confirm the account and environment**

```bash theme={null}
straddle agent-context --pretty
```

Check `runtime_context.environment`, `runtime_context.integration_type`, and `runtime_context.acting_account`. For SaaS or marketplace, select the account if needed and check again:

```bash theme={null}
straddle use-account ACCOUNT_ID
straddle agent-context --pretty
```

**2. Refresh customers and paykeys**

```bash theme={null}
straddle sync --resources customers,paykeys --full --max-pages 0 --strict --json
```

Confirm that both resources emit `sync_complete` and that the final `sync_summary` has `success: 2`, `warned: 0`, and `errored: 0`. Review any `sync_warning` or `sync_anomaly`, including those that accompany exit code zero, before treating the queue as complete.

**3. List the review items**

```bash theme={null}
straddle review-queue --json
```

To focus on customers:

```bash theme={null}
straddle review-queue --type customers --json
```

Use `--type paykeys` for paykeys. The default, `all`, includes both kinds.

**4. Retrieve the review details**

For an item with `kind: customer`:

```bash theme={null}
straddle customers review get-customer CUSTOMER_ID --data-source live --no-cache --json
```

For an item with `kind: paykey`:

```bash theme={null}
straddle paykeys review get PAYKEY_ID --data-source live --no-cache --json
```

Replace the placeholder with the item's `id`. Use the returned review information to determine what evidence or decision the case needs.

## Interpret the results

The report contains `count` and an `items` array. Each item includes:

| Field | Meaning |
| - | - |
| `id` and `kind` | Customer or paykey to review. |
| `status` | Stored status, `review`, used to select the item. |
| `name` | Customer name, or the paykey label with institution name as a fallback, when present. |
| `customer_id` | Related customer for a paykey, when present. |
| `created_at` and `age_days` | Resource creation time and elapsed whole days since creation. An unknown creation time produces `age_days: -1`. |

Items with known creation dates appear oldest first; unknown dates appear last. Use this ordering to locate older records. Review duration requires separate evidence of when the item entered `review`, because `age_days` measures the resource's age.

An empty queue means the stored records in the selected context contain no matching statuses. If you expected a case, confirm the context, review the sync results, and retrieve that item's current review details.

## Complete the investigation

Record the item ID, review findings, and the evidence or decision needed from the responsible reviewer. Use [customer identity guidance](https://docs.straddle.com/guides/identity/customers.md), [identity reasons](https://docs.straddle.com/guides/identity/reasons.md), and the [paykey guide](https://docs.straddle.com/guides/bridge/paykeys.md) to interpret the findings. After a decision, refresh the records and rerun the queue to confirm the updated state.


## Related topics

- [Payment operations playbooks](https://docs.straddle.com/playbooks/overview.md)
- [Review a customer](https://docs.straddle.com/api-reference/customers/review.md)
- [Identity verification overview](https://docs.straddle.com/guides/identity/overview.md)
- [WALDO: identity matching](https://docs.straddle.com/guides/resources/waldo.md)
- [Identity verification reason codes](https://docs.straddle.com/guides/identity/reasons.md)


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