User Guide
  • Introducing Dojah
  • GETTING STARTED
    • Quick Actions
  • IDENTITY VERIFICATION
    • Sandbox Test Data
    • Government Lookup
      • Individual Lookup
      • Business Lookup
      • Download Lookups
    • EasyOnboard
      • Verification flows
        • Configuring a flow
        • Verification Pages
          • User Data
          • Government Data
          • Business Data
          • Phone Number
          • Email
          • Business ID
          • Government-Issued ID
          • Liveness
          • Upload Other Documents
          • Signature
          • Questions
        • Fraud Check
        • Cost Breakdown
        • Integration
      • Verifications
    • Document Analysis
    • Address Verification
  • FRAUD MONITORING
    • AML Screening
      • User Screening
      • Business Screening
      • Download Screenings
    • EasyDetect
      • Creating a flow
        • Editing a Process
      • Connecting a flow
      • Cases and Events
        • Reviewing Cases
  • REPORTING ANALYTICS
    • API Report
    • Messaging Logs
    • Easy Detect Report
    • Easy Credit Check
  • Developers
    • APIs Logs
    • Configuration
      • Creating/Editing Apps
      • API Keys
        • Sandbox and Live Environment
      • Webhooks
  • Billings
    • Top-up Wallet
    • Transaction History
    • API Calls
  • Settings
    • Teams
      • Manage Teams and Permissions
      • Inviting Team-members
    • Audit logs
Powered by GitBook
On this page

Was this helpful?

  1. IDENTITY VERIFICATION
  2. EasyOnboard
  3. Verification flows

Fraud Check

With Fraud configuration, you can detect suspicious actions by setting rules and conditions that would serve as blockers to monitor fraud.

Last updated 3 months ago

Was this helpful?

You can detect fraud with the following:

  • Detect with user data: This ensures user's entered data on the verification page is compared to government data information. If there's a mismatch, businesses can choose to fail the verification, indicating that the provided information doesn't match the official records. Alternatively, they can choose to put the verification change the status of the verification to pending for manual review, allowing for a closer inspection before making a decision.

  • Detect with age limit: This ensures businesses can detect fraudulent activities comparing the date of birth entered by the user with the government data, businesses can determine whether there is a match or not. If there are discrepancies or inconsistencies, businesses can choose to fail the verification, indicating that the provided age doesn't match the official records. Alternatively, they can pend the verification for manual review.

  • Detect with Liveness: This ensures businesses can detect fraudulent activities with Glasses on and Brightness level. Businesses can check for certain factors like the presence of glasses and the brightness level in the captured image. If glasses are detected, it can be flagged as potentially suspicious or non-compliant with the verification requirements. Similarly, the brightness level can be analyzed to ensure that the image was taken in proper lighting conditions and not manipulated or taken from a pre-existing photograph.

  • Detect with AML Screening: With AML screening, businesses can cross-check user's information against the anti-money laundering list or watchlist. This list typically contains individuals or entities involved in money laundering, terrorism financing, or other financial crimes.

    By conducting AML screening during the onboarding process, businesses can identify if the user matches any entries on the list. If a match is found, it can be flagged as potentially high-risk or suspicious activity.

  • Detect with IP/Device Screening: By screening the IP address and device details of users, businesses can check if they are using an IP address that has been blacklisted due to previous fraudulent activities.

    If a user's IP address is flagged as blacklisted, it could indicate a higher risk of fraudulent behavior.