Skip to main content
ID check requires not only dashboard configuration but also API integration. This page provides comprehensive guidance on dashboard setup, API usage for different scenarios, webhook utilization, and liveform integration.

New Dashboard vs Old Dashboard Comparison

Check the differences between the old and new dashboards and where options have been relocated.

ID Check Best Experience Guide

A step-by-step setup guide for new customers. Follow the steps below to build an operational eKYC pipeline within a day.

5 Representative Scenarios

Purpose: Prevent fraudulent account creation before new account opening and card issuanceKey Settings:
  • Project Status: TEST → OPEN transition
  • Security Settings: Private mode + Token ID pre-registration + Encryption-only mode
  • Authentication Policy: ARGOS Score 80~85, duplicate user detection
  • Anti-Fraud: Streaming capture only, Proxy & VPN detection
Integration: Instant account/product activation via webhook upon approval
Purpose: Country-specific market onboarding, payment/withdrawal permission escalation (KYB/KYC)Key Settings:
  • Projects: Managed separately by region
  • Authentication Policy: Universal ID support, country-specific restrictions
  • Anti-Fraud: Regional pre-screening, issuing country verification
  • Security Settings: Regional access control via IP whitelist
Integration: Region-specific custom webhook settings
Purpose: Seller registration, identity verification before high-value product purchasesKey Settings:
  • Authentication Policy: Face duplicate check enabled (Selfie process required)
  • Anti-Fraud: Streaming capture only, Proxy & VPN detection
  • Submission Limiting: Window Sliding method for submission rate limiting
  • Duplicate Management: Duplicate check pipeline, duplicate approval/rejection prevention periods
Integration: Instant seller registration processing via webhook
Purpose: Adult verification, specific regional IP restrictions, retry/bot user filteringKey Settings:
  • Authentication Policy: Age limits, blacklist countries, automatic processing only
  • Anti-Fraud: Face-based age verification, regional pre-screening
  • Submission Limiting: Force block feature to block abusive users
  • Reviewer: ARGOS professional reviewers or Client API selection
Integration: Instant service access upon automatic approval
Purpose: High-risk customer screening, insurance underwriting, background checksKey Settings:
  • Additional Info: Up to 5 custom fields in Liveform step 2 (Text/Dropdown/Date/Phone/PDF upload)
  • Authentication Policy: Custom ARGOS Score + Client API review
  • Anti-Fraud: Multi-factor authentication (Government data verification, 1-won account verification, etc.)
  • AML: Watch list filtering + Ongoing Monitoring
Integration: Instant screening result delivery via webhook

Step-by-Step Setup Guide

1

1. Project Basic Information Setup

Set the project’s purpose and status.Location: Project Management > Project Settings > Project Info
  • Project Name: Enter an accurate service name that users can recognize
  • Project Logo: Upload a logo to distinguish projects in the dashboard
  • Project Status: TEST during setup, OPEN when transitioning to production
  • Liveform URL Check: Verify ID document / Knowledge-based pipeline URLs

Project Info Settings

View detailed setup instructions
2

2. Security and Access Control Setup

Prevent authentication link reuse, interception, and unauthorized access.Location: Project Management > Security Settings
  • Access Control: Private mode + Token ID pre-registration + Token expiration conditions
  • Data Protection: Liveform encryption settings (ECB/GCM) + Encryption-only mode
  • Secure Data Transfer: All data encrypted when calling APIs
3

3. KYC Process and Authentication Policy Setup

Decide “which submissions to automatically approve, and which to send for manual review.”Location: Project Management > Policy and Authentication > KYC Process
  • ARGOS Score Threshold: Higher scores mean stricter approval criteria (Recommended: Start with 80~85)
  • Automatic Processing Only: 100% automated operation without Pending
  • Age Limit: Automatic rejection for users below the set age
  • Blacklist Countries: Restrict IDs issued from specific countries

KYC Process

View detailed setup instructions
4

4. Authentication Data and Duplicate Management

Set up duplicate user detection and submission rate limiting.Location: Project Management > Policy and Authentication > Authentication Data
  • Duplicate Check Pipeline: Choose baseline method or custom DI
  • Submission Rate Limiting: Limit submission frequency using Window Sliding method
  • Duplicate Approval/Rejection Prevention Period: Prevent re-submission from already processed users

Authentication Data

View detailed setup instructions
5

5. Authentication Enhancement and Anti-Fraud Setup

Block account takeover/deepfake/screenshot/print attacks.Location: Project Management > Policy and Authentication > Anti-Fraud and Forgery Prevention
  • ID Forgery Prevention: MRZ check, PDF417 check, ID liveness
  • Face Authentication: Selfie process, face duplicate check, selfie liveness
  • Meta Information-Based Detection: Proxy & VPN detection, regional pre-screening
  • 3rd Party Data Sources: 1-won account verification, government data verification, etc.

Anti-Fraud and Forgery Prevention

View detailed setup instructions
6

6. AML (Anti-Money Laundering) Setup

Filter for sanctioned individuals, PEPs, and other high-risk persons.Location: Project Management > Policy and Authentication > AML
  • AML Watch list filtering: Set risk threshold, full date of birth match option
  • AML Ongoing Monitoring: Continuous monitoring through periodic re-screening

AML Settings

View detailed setup instructions
7

7. Integration Info and Webhook Setup

Receive instant notifications to your system when authentication is completed/approved/rejected.Location: Project Management > Project Settings > Integration Info
  • Webhook URL: HTTP POST to endpoint URL
  • Notification User Management: Set up daily webhook report email reception
  • Return URL: Set redirect URL after authentication completion
  • Dynamic Fields: Pass kycStatus, userid, email, submissionId, etc.
  • Return URL Encryption: Encrypt dynamic fields for transmission
Firewall Configuration RequiredFirewall configuration for IP address 52.78.194.237 is required to receive webhooks.

Integration Info

View detailed setup instructions
8

8. Legal Notices and Additional Info Collection

Additional information collection for legal compliance and high-risk customer screening.Location: Project Management > Project Settings > Additional Info
  • Legal Notices: Set Terms of Service URL, Privacy Policy URL
  • Additional Info Collection: Up to 5 custom fields (Text/Dropdown/Date/Phone/PDF/Checkbox)

Additional Info

View detailed setup instructions
9

9. System Operation Settings

Manage submission control, administrator settings, and reviewer settings.Location: Project Management > Project Settings > System Operation
  • Submission Control System: Emergency stop feature to halt all submissions
  • Personal Information Display: Blur personal information in the dashboard
  • Administrator Settings: Add/remove administrators, view login records
  • Reviewer Settings: Choose ARGOS professional reviewers or Client API
  • IP Whitelist: Allow dashboard and API access only from specified IPs

System Operation

View detailed setup instructions
10

10. Liveform Customization (Optional)

Provide a user experience that matches your brand.Location: Project Management > User Experience > Liveform Customization
  • Result page customization
  • Language-specific settings
  • Image and text customization

Liveform Customization

View detailed setup instructions

API Integration Guide

The dashboard is a configuration tool for enabling options, while actual operations are performed through APIs. Check the API usage methods for each scenario.

Scenario-Based API Usage Guide

Scenario: When you want to retrieve information about an already authenticated customerAPI to Use: GET /submissionUsage Methods:
  • Query by Submission ID: Check detailed information of a specific submission
  • Query by User ID: Retrieve all submissions for a specific user
  • Query by Email: Retrieve submissions by email address
  • Query by Date Range: Retrieve submission list by date range
# Query by Submission ID
curl -X GET 'https://rest-api.argosidentity.com/v3/submission?submission_id={submission_id}' \
  -H 'x-api-key: {yourAPIKey}'

# Query by User ID
curl -X GET 'https://rest-api.argosidentity.com/v3/submission?userid={userid}' \
  -H 'x-api-key: {yourAPIKey}'

# Query by Email
curl -X GET 'https://rest-api.argosidentity.com/v3/submission?email={email}' \
  -H 'x-api-key: {yourAPIKey}'

GET Submission API

View detailed API documentation
Scenario: When migrating from an existing system or inputting test dataAPI to Use: POST /submission/migrationUsage Methods:
  • Migrate user data from existing systems to ARGOS system
  • Generate sample data for test scenarios
  • Direct data submission in special situations
curl -X POST 'https://rest-api.argosidentity.com/v3/submission/migration' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: {yourAPIKey}' \
  -d '{
    "admin": "[email protected]",
    "email": "[email protected]",
    "fullName": "John Doe",
    "birthDate": "1990-01-01",
    "kycStatus": "approved",
    "idType": "passport",
    "issuingCountry": "USA",
    "nationality": "USA",
    "gender": "male",
    "userid": "user_12345",
    "cf1": "campaign_summer"
  }'
Submissions created using this API do not go through ARGOS’ standard verification process. The client is responsible for the accuracy and validity of the data.

POST Submission API

View detailed API documentation
Scenario: When using private mode to pre-register and manage Token IDsAPIs to Use: POST /token, GET /token, DELETE /tokenUsage Methods:
  • Token ID Pre-registration: Register up to 100,000 tokens using POST /token
  • Token ID Query: Check registered token list and status using GET /token
  • Token ID Deletion: Delete expired or unnecessary tokens using DELETE /token
# Token ID Pre-registration
curl -X POST 'https://rest-api.argosidentity.com/v3/token' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: {yourAPIKey}' \
  -d '{
    "token_ids": ["tok_abc123", "tok_def456", "tok_ghi789"]
  }'

# Token ID Query
curl -X GET 'https://rest-api.argosidentity.com/v3/token' \
  -H 'x-api-key: {yourAPIKey}'

# Token ID Deletion
curl -X DELETE 'https://rest-api.argosidentity.com/v3/token' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: {yourAPIKey}' \
  -d '{
    "token_ids": ["tok_abc123"]
  }'
Token ID Pre-registration RequirementIf you enable the “Live-form Token ID Pre-registration” option in Project Management > Security Settings > Access Control in the dashboard, only pre-registered Token IDs can be used.
Scenario: When using Client API reviewer to approve/reject submissionsAPIs to Use: PATCH /submission, POST /client-reviewUsage Methods:
  • Update Submission: Modify submission information using PATCH /submission
  • Client Review: Process approval/rejection using POST /client-review
# Update Submission
curl -X PATCH 'https://rest-api.argosidentity.com/v3/submission' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: {yourAPIKey}' \
  -d '{
    "submission_id": "sub_abc123",
    "kycStatus": "approved"
  }'

# Client Review
curl -X POST 'https://rest-api.argosidentity.com/v3/submission/client-review' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: {yourAPIKey}' \
  -d '{
    "submission_id": "sub_abc123",
    "kycStatus": "approved",
    "comment": "Additional review completed"
  }'

PATCH Submission API

View detailed API documentation

Webhook Utilization Guide

You can monitor and automate all stages of the KYC process in real-time through webhooks.

Webhook Event Types

Webhook TriggerWhen It OccursUsage Example
createdWhen a submission is createdSubmission start notification, progress tracking
submitWhen a submission is in Pending statusManual review required notification, assign to reviewer
approvedWhen a submission is approvedAccount activation, service access grant, approval notification
rejectedWhen a submission is rejectedRejection reason delivery, retry guidance
updatedWhen a submission is updatedStatus change tracking, log recording
retryWhen a retry occursRetry notification, user guidance
deleteWhen a submission is deletedDeletion log recording, data cleanup
token_expiredWhen a Token ID expiresToken reissuance, access blocking
injectionWhen injection is performedAdditional info collection completion notification
amlWhen AML search is completedHigh-risk person detection notification, additional review needed
aml_monitorWhen AML Ongoing Monitoring results are availableContinuous monitoring result notification

Webhook Setup Method

  1. Set Webhook URL in Dashboard
    • Enter webhook URL in Project Management > Project Settings > Integration Info
    • HTTPS protocol required
  2. Process Webhook Event Reception
    // Express.js example
    app.post('/webhook', (req, res) => {
      const { webhook_trigger, submission_id, kycStatus } = req.body;
      
      switch(webhook_trigger) {
        case 'approved':
          // Approval processing logic
          activateUserAccount(submission_id);
          break;
        case 'rejected':
          // Rejection processing logic
          notifyUserRejection(submission_id);
          break;
        case 'submit':
          // Pending processing logic
          assignToReviewer(submission_id);
          break;
      }
      
      res.status(200).send('OK');
    });
    
  3. Webhook Security Settings
    • Signature verification implementation recommended
    • IP Whitelist: 52.78.194.237 must be allowed

Webhook Event Guide

Check webhook event types and payload details

Liveform Query String Utilization

You can pre-fill user information or customize the process by adding Query Strings to the Liveform URL.

Basic Query String Parameters

ParameterDescriptionExample
pidProject ID (required)pid=proj_abc123
emailUser email[email protected]
useridInternal user IDuserid=user_12345
cf1, cf2, cf3Custom fieldscf1=campaign_summer&cf2=source_web
tokenidToken ID (required for private mode)tokenid=tok_abc123
sidSubmission ID (for injection)sid=sub_abc123&action=addveri

Query String Usage Examples

// Basic Liveform URL
const baseUrl = 'https://form.argosidentity.com';

// Pre-fill user information
const liveformUrl = `${baseUrl}?pid=${projectId}&email=${encodeURIComponent(email)}&userid=${userId}&cf1=${campaignId}`;

// Use private mode (Token ID required)
const privateUrl = `${baseUrl}?pid=${projectId}&tokenid=${tokenId}&email=${email}`;

// Injection (additional info collection)
const injectionUrl = `${baseUrl}?pid=${projectId}&sid=${submissionId}&action=addveri`;

// Knowledge-based pipeline
const knowledgeUrl = `${baseUrl}/knowledge?pid=${projectId}&email=${email}`;

Using Encrypted Query Strings

If you enable Encryption-only mode in the dashboard, all Query Strings must be encrypted.
// When using encryption-only mode
const encryptedData = encrypt({
  email: '[email protected]',
  userid: 'user_12345',
  cf1: 'campaign_summer'
}, encryptionKey);

const encryptedUrl = `${baseUrl}?pid=${projectId}&encrypted=${encryptedData}`;

Query String Guide

Check detailed Query String parameter guide

Re-verification and Add-on Utilization

You can use Add-on APIs when re-verification is needed for authenticated users.

Face Auth API (Face Authentication Re-verification)

Scenario: When you want to re-verify face authentication for an already authenticated user APIs to Use: POST /faceauth, GET /faceauth, DELETE /faceauth
# Create Face Auth
curl -X POST 'https://rest-api.argosidentity.com/v3/faceauth' \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: {yourAPIKey}' \
  -d '{
    "userid": "user_12345",
    "email": "[email protected]"
  }'

Face Auth API

Check Face Auth API detailed documentation

Using Multiple Projects Simultaneously

When operating multiple projects simultaneously, you must use separate API Keys and settings for each project.

Project-Specific API Key Management

// Project-specific API Key configuration
const projectConfigs = {
  production: {
    apiKey: 'prod_api_key_123',
    projectId: 'proj_prod_abc',
    webhookUrl: 'https://api.yourcompany.com/webhook/prod'
  },
  staging: {
    apiKey: 'staging_api_key_456',
    projectId: 'proj_staging_def',
    webhookUrl: 'https://api.yourcompany.com/webhook/staging'
  },
  test: {
    apiKey: 'test_api_key_789',
    projectId: 'proj_test_ghi',
    webhookUrl: 'https://api.yourcompany.com/webhook/test'
  }
};

// Project-specific API calls
function callAPI(projectName, endpoint, data) {
  const config = projectConfigs[projectName];
  return fetch(`https://rest-api.argosidentity.com/v3/${endpoint}`, {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'x-api-key': config.apiKey
    },
    body: JSON.stringify(data)
  });
}

Project-Specific Webhook Processing

// Project-specific webhook routing
app.post('/webhook/:project', (req, res) => {
  const { project } = req.params;
  const config = projectConfigs[project];
  
  // Project-specific processing logic
  handleWebhook(config, req.body);
  
  res.status(200).send('OK');
});
Project Management Tips
  • Each project has an independent API Key
  • You can set different webhook URLs for each project
  • Check and manage project-specific settings in the dashboard

Security

  • Private mode ON
  • Token ID pre-registration ON (1-time expiration)
  • Encryption-only mode ON
  • IP whitelist registration

Policy

  • ARGOS Score 80~85 start → adjust based on metrics
  • Duplicate check pipeline ON
  • Client API reviewer designation when needed

Anti-Fraud

  • Selfie liveness ≥85
  • Streaming capture only
  • Proxy & VPN detection ON
  • MRZ·PDF417 check ON

UX

  • Skip result page if unnecessary
  • Use encrypted Dynamic Fields

Common Issues and Solutions

Solution:
  1. Set Return URL in Project Management > Project Settings > Integration Info
  2. Enable Skip result page option
  3. Safely pass required parameters via Dynamic Fields (can be encrypted)
→ See Integration Info Settings
Checklist:
  1. Verify endpoint URL accuracy
  2. Check HTTPS/signature verification implementation
  3. Verify firewall allows webhook IP address 52.78.194.237
  4. Check test event reception
→ See Integration Info Settings
Solution:
  • Selfie process activation is a prerequisite
  • First enable selfie process in Project Management > Policy and Authentication > Anti-Fraud and Forgery Prevention
  • Adjust selfie threshold appropriately
→ See Anti-Fraud and Forgery Prevention
Solution:
  • Check option location changes in the New Dashboard vs Old Dashboard Comparison page
  • Most features have moved under the Project Management section
  • Use the search function at the top of the dashboard
→ See New Dashboard vs Old Dashboard Comparison