| Country and ID coverage | Are the exact ID types you need (passport, national ID, driver’s license, residence permit) supported in every country you serve? | ARGOS ID Check200+ countries and 4,000+ ID document types (as of July 2026): passports, national IDs, driver’s licenses and residence permits. For South Korea: national ID, driver’s license, passport and residence permit. Accepted countries and ID types are set per project. | Docs ↗ |
|---|
| Document authenticity | How does it catch forged or edited IDs, and IDs re-photographed from a copy or screen? | ARGOS ID CheckOCR data extraction plus MRZ checks, driver’s license barcode (PDF417) checks, ID liveness (detects copies and screen replays) and streaming capture. | Docs ↗ |
|---|
| Face match and liveness | Is liveness passive, active or both? Does it catch deepfakes and the same face signing up twice? | ARGOS ID CheckSelfie comparison against the ID photo, passive and active liveness to detect photos and deepfakes, and face-duplication checks across submissions. | Docs ↗ |
|---|
| AML screening | Is AML included or sold separately? Which risk categories, and is there ongoing monitoring? | ARGOS ID CheckIncluded. Name, date of birth and nationality are screened against PEP, sanctions (SAN), regulatory enforcement (REL), reputation risk (RRE) and POI data. Screening runs automatically when a submission is approved, or on demand via API. AML Ongoing Monitoring re-checks registered users and notifies you of changes. | Docs ↗ |
|---|
| Fraud signals | What else blocks abuse beyond the ID and the selfie? | ARGOS ID CheckProxy and VPN detection, device verification, duplicate-signup detection from name, date of birth, gender and nationality, and an age limit read from the ID. | Docs ↗ |
|---|
| Integration | Is there a hosted flow, or do you build the UI? How are results delivered? | ARGOS ID CheckA hosted Liveform (one URL, works on the web and in app WebViews, 26 languages), or the Verify engine APIs if you build your own UI. Results arrive by webhook, return URL and REST API. | Docs ↗ |
|---|
| Automated decisions and review | Can you set your own approval thresholds? Who reviews borderline cases? | ARGOS ID CheckARGOS Score thresholds (Conservative 70, Standard 50, Open 40), an automated-only mode and custom policy rules. Pending cases are reviewed in the dashboard or with POST /v3/submission/review, by ARGOS Expert Reviewer or your own team (Client API). | Docs ↗ |
|---|
| Data region | Where is identity data processed and stored? Can it stay in a specific country? | ARGOS ID CheckEach project runs in the US or KR (South Korea) region. KYC processing and data storage take place in the project’s region; some third-party integrations, such as IP lookup, use the US region. | Docs ↗ |
|---|
| Security and privacy | Which certifications? How is data encrypted, and how are deletion requests handled? | ARGOS ID CheckISO/IEC 27001 certified. TLS 1.2+ in transit, AES-256 encryption of sensitive fields at rest, and optional API and webhook payload encryption. Delete and partial-delete APIs handle GDPR and CCPA deletion requests. | Docs ↗ |
|---|
| Testing | Is there a sandbox, and does testing cost anything? | ARGOS ID CheckThere is no shared sandbox. You create a separate development or QA project, isolated from production, with its own API key, settings and credit balance. | Docs ↗ |
|---|
| Pricing model | Per verification, per check or subscription? Are failed or rejected attempts billed? | ARGOS ID CheckUsage-based, quoted by sales for your volume, countries and checks. Credits are deducted when a submission is created, so rejected or deleted submissions are billed. | Docs ↗ |
|---|
| Limits and switching | What are the API rate limits? Can you bring over existing verification records? | ARGOS ID CheckAll ID Check API endpoints currently allow 100,000 requests per day (resets at UTC); higher quotas can be requested. Existing records can be imported with the migration API (POST /v3/submission/migration), which skips ARGOS verification. | Docs ↗ |
|---|