When an end-user completes a verification transaction, the details are displayed in a transaction report.
This report is accessible from the Transactions section of your Berbix dashboard for the duration of your data retention policy.
Most of the information contained in this report can also be accessed via our API.
Transactions that have not yet been completed and have an
In-Progressstatus on the Transactions page still generate a transaction report, but contain incomplete data.
The primary purpose of the Transaction Report is to help you review transactions.
Depending on your use case, you may wish to review a subset of transactions rather than relying on the automated decision in all cases. Transactions with a “Review” action status can be manually addressed by a human on your team. You can configure what triggers a transaction being accepted, rejected, or sent for manual review through your Action Maps.
This article covers the following in detail:
- Status and Flags
- Additional Actions
- ID Check Data
- Face Match
- Session Information
- Other transactions with Identical ID
- Access Log
The transaction status panel is on the top left of the transaction report page. This panel provides a quick overview of the transaction status and the flags that may have contributed to the status decision.
When an end-user has input all required information, your Action Maps tell Berbix whether to assign an
Review status action. The statuses shown here are equivalent to the
action field in the API response.
If your use-case requires routing transactions into multiple unique review queues, you may see additional status actions. If you're interested in exploring this option, please reach out to [email protected] to discuss.
If transaction flags were triggered, they will be shown in the status panel. If no flags are displayed, such as in the
Accepted example above, it typically means Berbix did not detect anything out of the ordinary about the verification.
If you are unsure what a flag means, hover your cursor over it to reveal a tooltip.
Keep in mind that this summary includes any flags that were triggered, including those that may not have contributed to the status decision. In the
Rejected example above, four flags were raised. Depending on your Action Map, these flags may or may not have been the reason for the rejection.
To see a detailed breakdown of which flags contributed to the status decision, tap the
Action Map Triggered link. This will open a window that walks through the logic as determined by your Action Map.
Additional information available in the status panel includes the following:
- Updated Date: The timestamp for when the transaction was last edited, whether automatically or manually
- Expiration Date: The date and time when this transaction and all underlying data will be permanently deleted from the Berbix system. This time frame is determined by your data retention policy.
- Actions: Depending on the transaction status and on your user permissions, you may be able manually accept or reject the transaction, either as the initial decision following a
Reviewstatus, or as a system override.
- Additional Actions: As described below, the additional actions provide an opportunity escalate the transaction, block the ID from being accepted in future transactions, and permanently delete the transaction.
Escalating a transaction notifies the Berbix team so we can investigate further. Please escalate transactions if you believe the automated decision was incorrect, or if you feel we made an error in some way.
Block this ID
Blocking an ID enables you to prevent known bad actors from reentering your platform. When set, Berbix will raise a blocked flag that can be mapped to a reject action if this ID is used in a future transaction.
Deleting a transaction permanently deletes any data for a given transaction. This may also be done via API.
The ID Check section in the center of the report contains all of the data fields Berbix extracted from the document, plus the photos the user uploaded. Click on the photos for closer visual inspection, or to see alternate shots provided by the user.
ID Check: Confidence and Sources
Each field in the ID Check will have an associated color (green, yellow or red), corresponding to our confidence in the source of the data:
- Green, high confidence: Extracted from a machine readable source (2D barcode or MRZ)
- Yellow, medium confidence: Extracted through OCR of the text on the front of the ID (and sometimes confirmed by the user) or extracted from a 1D barcode.
- Red, low confidence: Data provided manually by the user only.
In the above example, all the fields have green confidence bars, indicating that the data was extracted from a machine-readable source on the document.
You may hover over the source bars to see and compare the values obtained from the different sources.
When Berbix detects inconsistencies in the information from different sources, you will see an exclamation mark next to that field. You may hover over the exclamation point for an explanation, and you may hover over the confidence bar for a comparison of what information was captured from each source.
ID Check: Document Images
By clicking on the thumbnail images of the document, you'll see the user-provided front or back images of the ID that can be used for manual review. Note: If any of the images shown on the details page are partially cropped, clicking on the image will reveal alternative scaled shots.
Images exposed in the dashboard (and via the API) are watermarked in an effort by Berbix to be the best possible steward of sensitive data. Image watermarks are generated on a per-access basis and therefore can be traced to the IP address accessing the image and the timestamp at which the image was accessed.
Images can include up to two watermarks: one in the bottom-left corner and one that covers the sensitive data in the image (such as an ID or a face). The IP address and timestamp associated with the image are also rendered in a notice at the bottom of the image to discourage storing or sharing of this sensitive information.
Watermarked images are also surfaced at a lower resolution than that of the original raw image. Please contact us if the resolution or watermark prevents you from reviewing the contents of a given ID or selfie image.
When a transaction's action is
review, Berbix automatically hides the larger watermarks within the dashboard in order to facilitate reviewers' efforts.
Additionally, Berbix offers the ability to selectively hide watermarks from the transaction report. To do this, click on the image you'd like to reveal, and select "Show without watermark" at the bottom of the modal. Please note that each time an image is revealed without watermarks the instance is logged and listed in the Logs page, and that watermark reveals are subject to a daily and monthly cap.
If you are using a selfie or liveness match as part of your verification flow, the resulting photos will be shown under “Face Match”. In this example, which triggered an “ID Selfie Mismatch” flag, the selfie photo has an alert because it does not appear to be a photo of the same person as the ID.
When available, session information can be visually compared to the address on the ID, or to subsequent sessions, as a check against suspicious activity.
If two or more transactions are created with different Customer UIDs, and there is meaningful overlap between the information extracted from the documents in each transaction (full name, date of birth, etc.) this is considered a duplicate transaction and linked here.
Berbix logs status changes on all transactions, and all watermark removals. These are stored on a per-transaction basis, and may also be accessed on the Logs page.
© Berbix Inc. All rights reserved.
Updated 1 day ago