Single Verification
You check a user only once. Verify, then Enroll.
Repeat Verification
You check the same user more than once. Enroll first, then Verify.
Single Verification
Use this pattern when a given user goes through ID Check exactly once and you will not re-check them. Common use cases- One-time KYC / identity verification at onboarding
- Age verification at sign-up
- Gating a single high-risk action (e.g. a first payout) with no later re-check
1
Verify
Call /verify-id to get the user’s Decision, Risk Score, and Risk Flags. See Response Signals for how to interpret everything the endpoint returns.
2
Enroll
Call Enroll to tie the session to your
account_id. This lets Verisoul match future sessions against enrolled accounts to prevent repeat devices, repeat faces, and repeat IDs from signing up.Repeat Verification
Use this pattern when the same user is checked more than once — for example when you run both ID Check and Face Match on a user, or re-verify a returning user. Common use cases- Running both ID Check and Face Match on the same user
- Re-verifying returning users at sign-in, withdrawals, or large transactions
- Fast-track level upgrades where a user re-verifies to raise their trust level
- Periodic or step-up re-verification
1
Enroll
Call Enroll to tie the new session to the same
account_id the user already uses. Verisoul now knows this session belongs to an existing account.2
Verify
Call /verify-id to get the user’s Decision, Risk Score, and Risk Flags. Because the session is already enrolled, prior sessions are recognized as the same account and are not counted against the user. See Response Signals for details.
