Skip to main content
Version: v2

Configure based on scenarios

The examples below show how different constraint profiles map to specific Verify configurations. They are illustrative—your configuration will depend on your risk tolerance, user motivation, and deployment context.

In-person, staff-assisted verification​

Constraints:

  • Staff are physically present during verification, eliminating screen and photocopy attacks
  • High false rejection cost: friction damages relationships with high-value or loyal customers
  • Fraud is unsophisticated and low-cost per incident
  • Manual intervention is available when a document is rejected

Industries: hotels, casinos, car rental, hospitality, age-gated venues

{
    "useCase": {
        "documentVerificationPolicy": "Permissive",
        "verificationContext": "InPerson",
        "manualReviewStrategy": "Never"
    },
    "options": {
        "photocopyMatchLevel": "Disabled",
        "screenMatchLevel": "Disabled"
    }
}

verificationContext: InPerson disables liveness checks. photocopyMatchLevel and screenMatchLevel are disabled because staff presence prevents these attack vectors.

High-conversion remote at physical locations​

Constraints:

  • App-based onboarding, but used at physical locations (malls, venues, transit hubs)
  • Low fraud risk and low fraud cost
  • High false rejection cost: a lost user costs more than the fraud it would have prevented
  • User motivation is low; any friction risks abandonment
  • Physical deployment makes printed photocopy attacks implausible in practice

Industries: micro-rental services, shared mobility (bikes, scooters), low-value asset tracking, vending

{
    "useCase": {
        "documentVerificationPolicy": "Permissive",
        "verificationContext": "Remote",
        "manualReviewStrategy": "Never"
    },
    "options": {
        "photocopyMatchLevel": "Disabled"
    }
}

verificationContext: Remote enables liveness checks by default. photocopyMatchLevel: Disabled removes the photocopy check, which is not a realistic attack vector at physical locations.

Balanced remote verification​

Constraints:

  • Deployed remotely
  • Low to moderate fraud risk and cost per incident
  • False rejections carry a moderate business cost
  • Users are moderately motivated

Industries: credit unions, community banks, lower-risk account opening, membership services

{
    "useCase": {
        "documentVerificationPolicy": "Standard",
        "verificationContext": "Remote",
        "manualReviewStrategy": "RejectedAndAccepted",
        "manualReviewSensitivity": "Low"
    }
}

Handling expired documents

Some regulations or local legislation may require accepting documents past their expiry date. To accept expired documents that are otherwise valid, set treatExpirationAsFraud to false:

{
    "useCase": {
        "documentVerificationPolicy": "Standard",
        "verificationContext": "Remote",
        "manualReviewStrategy": "RejectedAndAccepted",
        "manualReviewSensitivity": "Low"
    },
    "options": {
        "treatExpirationAsFraud": false
    }
}

High-assurance remote fraud prevention​

Constraints:

  • Deployed remotely
  • High fraud risk: fraudsters use fake documents to open accounts at scale
  • High fraud cost per incident; losses cannot be recovered through legal means
  • Users are motivated enough to tolerate moderate friction
  • False rejections are acceptable when they route to manual review

Industries: consumer lending, buy now pay later, fintech credit, short-term loans

{
    "useCase": {
        "documentVerificationPolicy": "Strict",
        "verificationContext": "Remote",
        "manualReviewStrategy": "RejectedOnly",
        "manualReviewSensitivity": "Default"
    }
}

False rejections are below 1% and most route to manual review. Around 1–2% of fraud attempts succeed, but documents cannot be reused, which limits attacker scalability.

Very high-assurance remote KYC​

Constraints:

  • Deployed remotely in a regulated industry with mandatory KYC
  • High fraud risk: account takeover and multi-account abuse are active threats
  • High fraud cost per incident
  • Users are highly motivated to complete onboarding (financial or access incentive)
  • False rejections are low-cost because motivated users retry without support intervention
  • A support team is available to review borderline cases

Industries: crypto exchanges, regulated investment platforms, online gambling, neobanks

{
    "useCase": {
        "documentVerificationPolicy": "Strict",
        "verificationContext": "Remote",
        "manualReviewStrategy": "AcceptedOnly",
        "manualReviewSensitivity": "Default"
    }
}

manualReviewStrategy: AcceptedOnly routes borderline accepted cases to manual review, catching fraud that Verify could not decisively reject. Users who were falsely rejected will typically retry on their own.

Last updated on