Use Cases


Learn about all of the latest product updates, every week

Nov 22
November 22

30% faster liveness verifications, fewer clicks to finish Screening reviews, SMS OTP autofill ๐Ÿ˜„


  • We simplified selfie checks, removing the requirement for users to turn their head to one side. We found this to be the most error-prone step (for example, confusing it with tilting versus turning the head). We adjusted the timing of the other steps accordingly allowing us to maintain the same security profile and improve pass rates

    Faster liveness checks

  • Automatically set the overall Screening status during a hit review to cleared or rejected based on the combination of confirmed and dismissed hits in a review

    Auto set screening status

  • Significantly improved the reliability of SMS OTP autocomplete when used through an iOS or Android WebView

  • We've improved our PEP database reducing the number of IZ_PEP individuals with no associated country codes or locations by 50%

  • Improved the robustness of IP address geocoding

  • Improved the design of the back button in Screening to match Flow's style

  • Updated the header for Screenings to match Flow for visual continuity

    New screening header design

  • The dashboard will now intelligently redirect you to products that are actually enabled on your account when you navigate to the root

  • If you have the secondary review feature enabled on Screening, we will now no longer show the "Two reviews are required" bar on Screenings with no hits to review to improve clarity

  • Breadcrumb navigation elements on the dashboard settings modal are now clickable

  • Added date of birth typo correction to Screening

    Date of birth typo correction

  • We no longer auto-asssign Screenings if their initial status is cleared

  • Loading liveness videos on the dashboard now display a loading spinner rather than appearing blank

  • Added additional sanity checks to date ranges of OCR'd data from ID documents


  • Fixed a visual glitch on the dashboard when a fallback step is expected on Flow but instead the session reached a terminal state
  • Fixed an overly strict assertion on the Screening dashboard that could cause errors when submitting reviews
  • More aggressively set liveness sessions to pending to make accidental page refreshes not end up in a stuck state for the end user
  • Fixed a visual issue where extracted ID doc names would get cut off by the container to their right
  • Fixed an issue where a liveness verification would not get processed if we couldn't extract a face from an ID document
  • Fixed a visual issue where our dashboard error bar would sit below on-screen elements rendering it difficult to read
  • Fixed an issue where sessions with manually approved steps could not be reflowed
  • Fixed an issue where the "Last saved at" timestamp would not be correctly updated on a Flow template
  • Fixed a bug where users who have "auto-assign" enabled on their Screening program could experience an API error when new hits were discovered
  • Fixed an issue where an ID document step could appear to have passed or failed but no results show on the dashboard
Nov 15
November 15

Politically Exposed Persons general availability, search by customer reference, and more manual overrides ๐Ÿ›๏ธ


  • ๐ŸŒ Our Politically Exposed Persons list is now available for all Screening customers. Choose between four risk levels based on your regulatory requirements and filter customers by location to reduce potential false positives. (API code: IZ_PEP)

    Choose a PEP level

  • ๐ŸŒ World Bank Listing of Ineligible Firms and Individuals List (API code: IZ_WBK) is now available for screening individuals and entities

  • Added the ability to search for Flow sessions by customer reference on the dashboard

    Search by customer reference

  • Added the ability to manually approve or reject the Flow Lightning Verification step

  • Added the ability to manually approve or reject the Flow Selfie Check step

  • Added the ability to confirm or dismiss all hits at once in the Screening dashboard

    Confirm or dismiss all hits


  • Substantially improved the reliability of flow_session.step.updated webhook events
  • Improved the reliability of the Flow Risk Check step. It was previously possible for some sessions to get stuck in a processing state
  • Improved the reliability of the Flow Selfie Check step. It was previously possible for some sessions to get stuck in a processing state
  • Increased the combined limit of hits that can be reviewed at one time when screening individuals from 50 to 100.
  • Adjusted the Lightning national ID collection settings to make the configuration options clearer
  • Made it possible to retry certain failed SMS verification attempts with a new phone number
  • Removed several full reloads on the dashboard making for a snappier navigation experience
  • The loading animation when moving between screening statuses, assignments, etc. is now less jarring


  • Fixed bug which allowed configuring Lightning national ID collection in a way that made passing the Flow session impossible. Now if you choose not to collect a national ID, the relevant ruleset will be updated to take that into account.
  • Fixed bug where the "Assignee" dropdown for filtering screenings would incorrectly have two entries for the current user
  • Fixed date extraction issue for some Korean and Japanese IDs
  • Fixed bug where dismissed hits were not displaying correctly in the dashboard
  • Fixed issue where the contents for Flow Network Explorer could overflow improperly
  • Fixed a bug where the "Continue" button of the Flow modal would not automatically pop up when an address was completed for locales without postal codes or zones
Nov 8
November 8

Introducing the Flow Network Explorer, and a more reliable, faster Flow ๐Ÿงญ


  • We're excited to announce the Flow Network Explorer. Flow is always trying to block fraudulent verification attempts, and one of the most powerful tools we use involves understanding the velocities of various characteristics of users signing up for your platform. Today we use Device IDs and IP address and plan to expand it more over time.

    The Flow Network Explorer lets you view a list of all historical Flow sessions that are related in some way to the current session, such as users who signed up multiple times using the same device, or perhaps a shared internet connection. This helps you understand the graph of potentially fraudulent users and shut them down proactively.

    Faster opening speeds

    Flow Network Explorer

  • You can now expire API keys that are no longer in use via the dashboard. No more contacting support to roll API keys!

  • ๐Ÿ‡ช๐Ÿ‡บ Interpol Red Notices for Wanted Persons List (API code: IZ_IPL) is now available for screening individuals

  • ๐Ÿ‡บ๐Ÿ‡ธ FBI Wanted List (API code: US_FBI) is now available for screening individuals

  • ๐ŸŒ State Owned Enterprises List (API code: IZ_SOE) is now available for screening entities


  • Improved the back button navigation behavior on the Flow dashboard. The back button will now remember which page you were last on so you don't lose your place when investigating sessions

  • We've improved the time to first launch the Flow modal for your users by 30% - 50% with a significant decrease in variability

    Faster opening speeds

  • ID documents will now be uploaded to hyper-local servers, speeding up uploads by 20% - 600% depending on the country/region where the upload takes place

  • Significantly improved the reliability of liveness verifications

  • Added additional country flags to help readability of ID document metadata

  • Lightning verifications will now show PO Box and address type information on the dashboard

  • Added a new animation to liveness verifications to make head turning instructions clearer

  • Added links to view raw, uncropped ID document images to the dashboard

  • Manual approval has been added to risk checks

    Override risk checks

  • Improved OCR performance of ๐Ÿ‡ฎ๐Ÿ‡ณ Indian ID documents, and ID documents with diacritics such as those in ๐Ÿ‡น๐Ÿ‡ท Turkey, ๐Ÿ‡ซ๐Ÿ‡ท France, and ๐Ÿ‡ณ๐Ÿ‡ฟ New Zealand


  • Fixed an bug where you could disable the Screening setting for requiring all reviews to be submitted before you can change its status without disabling the Four Eyes review system
  • Fixed an issue where Flow step interstitials had incorrect behavior if the next step is yet to be determined
  • Fixed an error on the Flow dashboard for when a session can't be fingerprinted
  • Fixed an issue where when checking image metadata for ID documents, a missing timezone offset could cause an error
  • Fixed an issue where reflows would contribute to a user's Flow Network velocity
  • Fixed an issue where manually approved or rejected Flow session steps were not considered terminal events
  • Fixed an issue on Webkit browsers where icons would have incorrect hover states on the dashboard
  • Fixed an issue where "No Data" would be shown for US Lightning verifications on the top level breakdown, but constituent traits had matching information
  • Fixed an issue where webhooks were not being emitted for manually approved or rejected Flow steps
  • Fixed an issue where changing between ID document attempts could cause ID document pictures to not be rendered
  • Fixed an issue with Flow sessions erroring out when ISP type cannot be determined
  • Fixed an issue where entering a long address line2 could result in a front-end error when completing a Flow session
  • Resolved an inconsistent design between Flow steps that have yet to be completed
  • Fixed an issue where date of birth was not extracted from Canadian drivers licenses
  • Fixed an issue with reading ID documents with hyphenated names
Nov 3
November 3

Manual review overrides for ID documents, higher ID document pass rates, Flow feedback system โ†ฉ๏ธ


  • If an ID document fails verification, you can now override the system's decision and allow the Flow session to continue. We'll be adding overrides to more step types soon!

Override ID document decisions

  • ๐Ÿ‡บ๐Ÿ‡ธ Non-SDN Chinese Military-Industrial Complex Companies List (API code: US_CMC) is now available for screening entities
  • You are now able to report any issues with a Flow session from within the dashboard. This helps improve the feedback loop of letting the Cognito team know when you discover parts of a verification that had unexpected outcomes so they can be fixed as quickly as possible

Report a problem modal


  • ID document verifications will now use MRZ-extracted date of birth information to augment OCR extractions
  • We have further improved international name matching between user input and information extracted via OCR. Vietnamese, Cyrillic, Korean, and Chinese character matching now has a higher chance of a transliteration match to Latin user inputs
  • We now show a helpful message on the dashboard to show when a user is still inputting data during a Lightning verification
  • Added EPIC ID number support for ๐Ÿ‡ฎ๐Ÿ‡ณ Indian Lightning verifications
  • We've improved the interface for selecting watchlists for Screening to provide helpful information about the lists that are available and what they screen against New watchlist selector


  • Fixed an issue where ID documents with erroneously submitted backs would fail
  • Fixed an issue with porting PII over during reflow attempts
  • Fixed an issue where ID documents would incorrectly OCR country codes and would get stuck in our queue
  • Fixed an issue with Kosovo ID documents would get stuck due to inconsistent country codes
  • Fixed an issue where SSN last4 validation was too strict
  • Fixed an issue where some ๐Ÿ‡ณ๐Ÿ‡ฑ Dutch Lightning verifications could error out
  • Fixed an overly strict validation on Australian passport numbers
Oct 25
October 25

Added US BIS Unverified entity list, Flow modal fine-tuning, and a speedier dashboard ๐Ÿ’จ


  • ๐Ÿ‡บ๐Ÿ‡ธ US Bureau of Industry and Security Unverified List (API code: US_UVL) is now available for screening entities


  • Redundant, leading digits in phone numbers are now automatically removed for Flow end-users
  • Significantly improved the performance of Flow dashboard index pages, especially for users with a large number of sessions
  • Removed redundant Continue button from the SMS code Flow step which submits automatically when the code is entered
  • Adjusted styling of the Flow country selection modal to be less cramped


  • Bug temporarily preventing new Flow Template updates
  • Fixed a typo in an SMS delivery failure message and a developer-facing warning
  • Fixed a bug where ID documents from US territories would crash the dashboard
  • Fixed an issue where duplicate Screenings could be created if the New Screening button was clicked more than once in rapid succession
  • Fixed a race condition that could delay Flow session step processing
  • Fixed an issue with Hybrid Flow verifications where a 400 status code would be returned, but a session would still be persisted