Skip to main content
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 and configure an API key with access to the customers and paykeys you want to review.
  • Confirm your environment, integration type, and acting account.
  • 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

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:
2

Refresh customers and paykeys

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

To focus on customers:
Use --type paykeys for paykeys. The default, all, includes both kinds.
4

Retrieve the review details

For an item with kind: customer:
For an item with kind: paykey:
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: 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, identity reasons, and the paykey guide to interpret the findings. After a decision, refresh the records and rerun the queue to confirm the updated state.