Skip to main content
This page is a guide for those setting up ARGOS ID check for the first time. Follow the guide below to create an operational eKYC pipeline within a day. Each step is explained in the order of “Why it’s needed → Where to enable it → Recommended values”.

5 Representative Scenarios

How: Safely transition from pilot to production by switching project status from TEST→OPEN in stages. Use the ID document flow for liveform, and block link reuse and interception with Private mode + Token ID + Encryption-only mode in the admin console.Where: Attach before new account opening or card issuance to block fraudulent signups, and instantly activate accounts/products upon approval via webhook.
How: Separate projects by region to partition administrator access permissions, and set policies like universal ID support and country restrictions differently for each region.Where: Country-specific market onboarding, payment/withdrawal permission elevation (KYB/KYC) stages.
How: Enable face duplicate check (prerequisite: Selfie process ON), allow streaming capture only, and reduce tool/screen attacks with Proxy/VPN detection.Where: Seller registration, identity verification before high-value purchases, re-verification of users with frequent refunds/disputes.
How: Use age restrictions, blacklist countries, and automatic processing only to quickly filter out what needs filtering, and handle pending cases through manual review or API review.Where: Adult verification, specific region IP restrictions, retry/bot-like user filtering.
How: Configure up to 5 additional information fields in liveform step 2 to collect evidence through text/dropdown/date/phone number and PDF upload (1MB).Where: High-risk customer review, insurance underwriting, employment background checks.

Step-by-Step Settings Guide

1

Open Project & Choose Pipeline

Operation and restrictions differ based on project purpose (test/production). Liveform URLs provide two authentication flows (ID document / Knowledge-based).
  • Where: Dashboard → Settings → Project Overview/Status
  • Status: 4 types: TRIAL / TEST / OPEN / CLOSE
  • Recommended: TEST during setup, OPEN when transitioning to production

Pipeline URL and Data Security

View detailed settings
2

Brand, Terms, and Completion Flow (Return URL)

Smoothly connect users to your product from the first screen. Logo and terms/privacy policy links automatically add legal consent UI, and after authentication you can choose 3-second auto-redirect to Return URL or Skip result page.
  • Where: Dashboard → Project Information
  • Recommended: Use service name that users recognize for logo/service name; if result page is unnecessary, use Skip result page + encrypted Dynamic Fields combination

Project Information Settings

View detailed settings
3

Link & Data Security (Private/Token/Encryption/IP)

You need to prevent authentication link reuse, interception, and unauthorized access.
  • Private Mode: Block authentication completion URL reuse (requires: Token ID)
  • Token ID: Usage count 1-time or time-based expiration
  • Encryption-only Mode: Allow only encrypted URLs (ECB/GCM selection)
  • IP Whitelist: Allow access only from specified IPs

Pipeline URL and Data Security

View detailed settings
4

Basic Authentication Policy (Automation Threshold/Duplicates/Age, etc.)

The core of deciding “which cases to auto-approve vs send to manual review.”
  • ARGOS Score Threshold: Higher scores = stricter approval criteria
  • Automatic Processing Only: 100% automated operation without Pending
  • Duplicate User Detection: Duplicate policy using default fields or Custom DI

User Authentication Policy Settings

View detailed settings
5

Multi-factor Authentication & Fraud Prevention (Selfie/Face Duplicate/Proxy, etc.)

You need to block account takeover, deepfakes, and screen capture/printout attacks.
  • Multi-factor Authentication: Government data verification, 1 KRW account verification, selfie process, face duplicate check
  • Fraud Prevention: Streaming capture only, Proxy & VPN detection, MRZ/PDF417 check

Multi-factor Auth & Fraud Prevention Settings

View detailed settings
6

Additional Information Collection (EDD/Evidence/Contact)

Additional documents and factual verification are needed for high-risk or specific industries.
  • Add up to 5 items
  • Types: Text/Dropdown/Date/Phone Number/PDF Upload/Checkbox

Additional Information Collection Settings

View detailed settings
7

Webhook Integration (Real-time Notifications & Automation)

Receive immediate notifications to your system upon authentication completion/approval/rejection for automation.
  • HTTP POST to Endpoint URL
  • Email notification settings available
  • HTTPS/signature verification implementation recommended

Webhook Settings

View detailed settings
8

AML: Watch List Filtering and Ongoing Monitoring

You need to filter for sanctions, PEP, and other risk persons.
  • Directly set risk threshold
  • Minimize same-name false positives with full date of birth match option
  • Periodic re-screening with Ongoing Monitoring

AML Settings

View detailed settings

Security

  • Private ON
  • Token 1-time expiration
  • Encryption-only ON
  • IP whitelist registered

Policy

  • Start ARGOS Score at 80-85 → Adjust based on metrics
  • Duplicate user detection ON
  • Assign Pending reviewer if needed

Fraud Prevention

  • Liveness ≥85
  • Streaming capture only
  • Proxy & VPN detection ON
  • MRZ/PDF417 check ON

UX

  • Skip result page if unnecessary
  • Use encrypted Dynamic Fields

Common Situations and Solutions

Set Return URL and enable Skip result page. Pass required parameters securely using Dynamic Fields (encryption available).→ See Project Information Settings
Check in this order:
  1. Verify Endpoint URL accuracy
  2. HTTPS/signature verification implementation
  3. Allow project-specific fixed webhook IP (firewall)
  4. Confirm test event receipt
→ See Webhook Settings
Selfie process activation is a prerequisite. Also adjust selfie threshold appropriately.→ See Multi-factor Auth & Fraud Prevention Settings