Skip to main content
Sometimes, the system may flag a verification as Suspected or Denied due to specific data tags. These tags appear when the information extracted from the document does not strictly match the data provided by your system (via API/Token) or your configuration rules. You can manually resolve these issues instantly by removing the specific Mismatch Tag that triggered the alert.

​
The Solution: Removing Tags

If you review a verification and determine that the discrepancy is acceptable, you can remove the mismatch tag to validate the session.

​
How to Remove a Mismatch Tag

  1. Open Verification: Navigate to the specific verification profile in your dashboard.
  2. Locate Tags: Look for the Mismatch tags section (located in the “Partner information” under “User data” card).
  3. Click ‘X’: Find the specific tag you wish to clear (e.g., NAME or OVER_AGE ) and click the ‘X’ icon next to it.
  4. Confirm Action: A pop-up window will appear asking:_“Are you sure you want to remove [TAG_NAME] mismatch tag?”_Click Confirm to proceed.
Important: Removing a tag is a permanent action for the current session. Once removed, the tag will not reappear or be re-triggered automatically, even if you refresh the page.
Automatic Status Update: Once you remove the tag, the system automatically re-evaluates the verification status.
  • If the tag was the only reason for rejection, the status will automatically change from Suspected/Denied to Approved.
  • You do not need to click the “Approve” button manually after removing the tag.

​
False Positive vs. Policy Override

It is important to distinguish between fixing a system error and making a conscious exception. Removing a tag works for both scenarios.

​
1. False Positive (System Error)

  • Scenario: The user is named “John”, but the automated system read “Jon” and applied a NAME mismatch tag.
  • Action: You remove the tag to correct the mistake.

​
2. Policy Override (Exception)

  • Scenario: You have set a minimum age of 18 in your configuration. A 17-year-old user applies, and the system correctly flags them with an UNDER_AGE tag.
  • Action: If you decide to make a business exception for this specific user, you can remove the UNDER_AGE tag to bypass the rule.
  • Result: The system will treat the user as compliant and change the status to Approved, effectively overriding your age policy for this one session.
Full Mismatch Tag Reference For a complete list of all mismatch tags and their detailed definitions, please refer to our [https://idenfy-ivs.atlassian.net/servicedesk/customer/portal/1)