Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.didit.me/llms.txt

Use this file to discover all available pages before exploring further.

Our Phone Verification process includes a series of automated checks to ensure the validity and security of the phone numbers being verified. This page outlines the potential warnings and errors you might encounter during the phone verification process.

​
Automatic Decline Conditions

The following conditions can result in an automatic decline depending on your application settings:
  • VERIFICATION_CODE_ATTEMPTS_EXCEEDED - The user has exceeded the maximum attempts to enter the correct code
  • HIGH_RISK_PHONE_NUMBER - The phone number is identified as a high risk number
  • PHONE_NUMBER_IN_BLOCKLIST - The phone number is in the blocklist

​
Configurable Verification Settings

Applications can configure how the system handles various verification issues by setting actions for different risk categories:
  1. Number Type
    • Risks: VOIP_NUMBER_DETECTED
    • Configurable action: Decline, Review, or Approve
  2. Risk Level
    • Risks: DISPOSABLE_NUMBER_DETECTED
    • Configurable action: Decline, Review, or Approve
  3. Duplicated Number
    • Risks: DUPLICATED_PHONE_NUMBER
    • Configurable action: Decline, Review, or Approve

​
Verification Attempt Limits

The system imposes limits on verification attempts to prevent abuse and maintain security:
  • Code Entry Attempts: Maximum 2 attempts to enter the correct verification code
  • Code Resend Requests: Maximum 2 requests to resend a verification code within 24 hours
You can customize these attempt limits in your application settings to match your specific security requirements and user experience needs.

​
Phone Verification Warnings

TagDescription
VERIFICATION_CODE_ATTEMPTS_EXCEEDEDThe user has exceeded the maximum number of attempts to enter the correct verification code.
HIGH_RISK_PHONE_NUMBERThe phone number is identified as a high risk number.
PHONE_NUMBER_IN_BLOCKLISTThe phone number is in the blocklist.
DISPOSABLE_NUMBER_DETECTEDThe phone number has been identified as temporary or disposable, often used to avoid verification traceability.
VOIP_NUMBER_DETECTEDThe phone number appears to be a Voice over IP (VoIP) number rather than a standard mobile or landline number.
DUPLICATED_PHONE_NUMBERThe phone number has been identified as a duplicate of a previously verified number.

​
Cross-Session Matches

When the same phone number is detected across sessions belonging to different users, the system records these as matches on the phone verification response. The system also checks your Blocklist — if the phone number was manually added to a blocklist, it appears as a match with source: "list_entry". Sessions are grouped by vendor_data: sessions with the same vendor_data are treated as the same user and excluded from matches. Without vendor_data, every session is treated as a unique user and all potential duplicates are surfaced. Each match includes the session_id, session_number, vendor_data, verification_date, phone_number, status, and is_blocklisted flag. Matches are returned in the matches array on V3 decision endpoints under phone_verifications.

​
Warning Types

Each risk is assigned a warning type based on your application’s configuration settings. Warnings fall into three severity categories: