Transaction Flags

A list of all possible flags that Berbix Verify provides upon transaction completion.

Transaction Flags are returned by Berbix upon the successful completion of a transaction by the end-user to identify items of note.

A triggered transaction flag does not necessarily mean that fraud has been attempted. Rather, flags identify transaction attributes that may impact the downstream decision to accept or reject the verification.

Transaction Flags are returned in the flags array of the Get transaction verifications response and are associated with Action Maps in the Berbix dashboard.

Data Flags

ID Data:

  • id_under_18: At the time the transaction was completed, the date of birth was less than 18 years ago.
  • id_under_21: At the time the transaction was completed, the date of birth was less than 21 years ago.
  • id_expired: At the time the transaction was completed, the expiry date was in the past.
  • id_expiry_extended: The expiry date has been extended.
  • id_expiry_unknown: The expiry date is unknown.
  • id_age_unknown: The date of birth is unknown.
  • id_sample_detected: The provided ID was a sample ID that is inauthentic for that user.

Comparative Data

  • id_duplicate_detected: A user with a different customer UID provided an ID with the same information (name, date of birth, expiration date, serial number, etc.) in a previous transaction within your retention period.
  • id_duplicate_possible: A user with a different customer UID provided an ID with similar information (name, date of birth) in a previous transaction within your retention period.
  • id_duplicate_face_detected: Another user provided an ID with a similar face in a previous transaction within your retention period.
  • id_blocked: The end-user uploaded a document that has been previously blocked.
  • id_blocked_possible: The end-user uploaded a document that has similar information (name, date of birth) to one that has been previously blocked.

Flags associated with comparisons across multiple users are only available if you provide a customer UID in the Create transaction request or when creating the hosted transaction.

Evaluation of Data (U.S. and Canada drivers licenses and government-issued non-driver photo IDs only):

  • id_fake_possible: The user provided an ID that might be inauthentic.
  • id_fake_likely: The user provided an ID that is likely to be inauthentic.
  • id_image_tampering_likely: The user provided a document that is likely to have been edited.

📘

"Possible" and "Likely" flags

The models that determine our flags with possible and likely qualifiers are frequently adjusted by our fraud prevention team to address new fraud trends and technologies we observe across the board.

When using these flags in your business logic, keep in mind that likely flags are a more confident assessment than possible flags.

Verification of Data:

  • id_user_confirmed: The user was prompted to confirm the name, date of birth, and expiration date we captured automatically, and they manually verified accuracy.
  • id_user_confirmed_advanced [Beta]: The user was prompted to confirm the name, date of birth, expiration date, ID type, ID issuer (country and state/province) and ID number, and they manually verified accuracy. To opt in to the beta, please reach out to [email protected]
  • id_manual_entry: Some data was provided manually by the user and was not verified by Berbix.

📘

Manually entered data?

If we are unable to parse some or all expected data in an ID document, we will ask the end-user to manually input information such as name, date of birth, and expiration date.

When this happens, we may not return certain flags to avoid the risk of relying on unverified data points. For this reason, we typically recommend using the review or reject action for transactions that flag id_manual_entry.

ID Front Flags

  • id_text_unreadable: We were unable to parse the human readable text in the front image.
  • id_no_face_detected: No face was detected in the front image of the ID.
  • id_too_many_faces_detected: The image provided included more faces than expected for the ID type.
  • id_mrz_parse_error: We were unable to parse machine readable content on the ID.
  • id_partial_mrz_read: Only part of the machine readable zone was successfully read from the scanned image.
  • id_front_suspicious: The front image(s) were flagged as suspicious and warrant further review. This flag may be triggered when a screen photo is detected, or when the picture provided at the selfie or liveness stage appears to be the picture on the front of the ID.
  • id_front_error_unknown: An unspecified error occurred when attempting to read the front image of the ID.

ID Back Flags

  • id_back_text_unreadable: Insufficient text was detected in the back image.
  • id_no_barcode_detected: No 2D barcode was detected in the back image.
  • id_incomplete_barcode_detected: A partial 2D barcode was detected in the back image. Check out our Frequently Asked Questions for additional context.
  • id_barcode_decode_failed: A full 2D barcode was detected in the back image but could not be decoded.
  • id_back_suspicious: The back image(s) were flagged as suspicious and warrant further review. This flag may be triggered when a screen photo is detected, or when tampering may be indicated.
  • id_back_error_unknown: An unspecified error occurred when attempting to read the back image of the ID.
  • id_barcode_parse_error: a full 2D barcode was detected and decoded but the data was in an unsupported format.

📘

Smart back flags

The types of flags you can expect depend on the type of ID uploaded.

If we're expecting a barcode on the back and that barcode cannot be successfully decoded, we return one of the following flags: id_no_barcode_detected, id_incomplete_barcode_detected, id_barcode_decode_failed, or id_barcode_parse_error.

Similarly, if we're expecting text on the back (e.g. most European IDs) and cannot find any, the id_back_text_unreadable flag is returned.

Selfie Flags

  • id_selfie_no_face_detected: No face was detected in the selfie image
  • id_selfie_too_many_faces_detected: The selfie was rejected for having too many faces.
  • id_selfie_direction_failed: The user was unable to take a valid selfie looking at the camera.
  • id_selfie_suspicious: The user provided selfie images that were unlikely to be genuine.
  • id_selfie_error_unknown: An unspecified error occurred when attempting to process the selfie.
  • id_selfie_image_tampering_likely: The user provided a selfie that is likely to have been edited.

Liveness Flags

  • id_liveness_no_face_detected: No face was detected in the liveness image.
  • id_liveness_too_many_faces_detected: The liveness image was rejected for having too many faces.
  • id_liveness_challenge_failed: The user was unable to satisfy the presented liveness challenge.
  • id_liveness_suspicious: The user provided liveness images that were unlikely to be genuine.
  • id_liveness_error_unknown: An unspecified error occurred when attempting to process the liveness image.

Consistency Flags

  • id_front_back_mismatch: The information scanned for the front is significantly different from the information drawn from the back. This is only applicable if machine readable components are collected.
  • id_selfie_face_mismatch: The similarity score between the selfie and the photo from the ID was too low.
  • id_selfie_face_mismatch_possible: The similarity score between the selfie and the photo from the ID is inconclusive.
  • id_selfie_face_comparison_unavailable: A similarity score between the front and selfie could not be determined.
  • id_liveness_face_mismatch: The similarity score between the selfie and the liveness photo was too low.
  • id_liveness_face_comparison_unavailable: A similarity score between selfie and liveness could not be determined.
  • id_selfie_consent_declined: the user did not provide consent to digitally compare the faces across images where applicable. If this flag is returned, we did not compare the face in the ID to the selfie and/or liveness photos and we recommend a manual review.
  • id_type_selection_mismatch: The type of ID uploaded by the user does not match the type that they selected. This flag may be present if you have [configured]
  • id_type_selection_mismatch_possible: The type of ID uploaded by the user may not match the type that they selected. This is a lower confidence version of the flag above. (https://docs.berbix.com/docs/templates#photo-id-flow-customization) only certain ID types to be acceptable in your template.
  • id_issuer_selection_mismatch: The country that issued the ID uploaded by the user does not match the country they selected. This flag will only be presented if acceptable country issuers have been configured in the template.
  • id_issuer_selection_mismatch_possible: The country that issued the ID uploaded by the user may not match the country they selected. This is a lower confidence version of the flag above.

© Berbix Inc. All rights reserved.