Review Queues contain transactions that may require manual review or additional actions. Review Queues are populated based on the decision logic configured in your Action Maps.
The Review Queues page provides an overview of all available Review Queues in your Dashboard.
By default, all Berbix dashboards include a
Default queue populated by your
Review action. Please reach out to [email protected] if you'd like to add additional queues.
In the example below, our Default Review Queue has 10 unreviewed transactions.
When you open a specific Review Queue, you'll see all the outstanding transactions that need to be manually reviewed.
In the top left, you can filter results by
Not Reviewed or
All transactions in the queue.
Berbix will also present the following additional info:
Claimed By: the Berbix dashboard user that claimed the transaction for review.
Review Created At: the time the transaction was queued for review.
Reviewer: the Berbix dashboard user that reviewed the transaction. This field is populated after an
actionhas been manually selected.
Reviewed at: the review time for the transaction.
When claiming a transaction for review, you can:
Claiman individual transaction
Claim 10to claim the oldest unclaimed 10 transactions
Claim allto claim all of the unclaimed transactions
10 will automatically open your oldest transaction for review.
When you select a transaction to review, you'll open the full Transaction Report for that transaction.
You will find a summary supporting the
Review decision in the Status section, and you may examine the details by clicking the "Action Map Triggered" link.
Once you have fully reviewed the Transaction Report and made a determination, select
After selecting an action, you have the option to provide context for your decision before pressing the Submit button.
If you have claimed additional transactions for review, the next transaction will open automatically.
Additional actions available include escalating the transaction to Berbix for review, blocking the ID from passing further transactions, and deleting the transaction.
Webhooks can be configured to be triggered when transactions are added to a review queue, by setting up a webhook of type
Verification finished and determining whether a review is required based on the
action included in the webhook payload.
© Berbix Inc. All rights reserved.
Updated 3 months ago