Online authentication (eKYC) with trust and efficiency at the same time!

Did you know that there is a steady improvement in improving the stability and efficiency of the ID check every month?

In this May update, features that greatly improve the security and flexibility of the ID check service were added. We strengthened the duplicate user detection, raised the security of the injection stage, and the WebHook trigger worked smarter.

Let's take a look at the three core features updated this time.

1. User Duplicate Detection Function (Custom DI)

You can now manage user accounts more precisely to ensure that a single person cannot create multiple accounts. A new duplicate user detection feature has been introduced, allowing administrators to define their own detection standards.

For example, if a user submits the same device, a similar face, or the same document, the system filters it in real time.

This allows platforms to block fraudulent users who repeatedly attempt to sign up such as reward abusers or event hunters. In short, operational costs are reduced, and user trust is enhanced.

Where to find it:
Dashboard → Settings → User Policy → Custom DI
You can view detection results in the Duplicate User Detection menu.

A Quick Note!

DI stands for “Derived Identifier” a secure replacement for traditional identification information. It’s a security technology that creates and uses a unique identifier for each user without storing sensitive personal data, such as social security numbers or passport numbers.

Why is DI important?

• Enhanced Personal Data Protection:
  Because DI replaces sensitive information, you can store only the DI without legal or security risks tied to data like social security numbers.

• Duplicate User Detection:
  Even if the same person verifies their identity multiple times, the same DI value is generated, enabling accurate detection of duplicates.

• Cross-Service User Matching:
  The same user can be uniquely identified across different systems using the same DI.
  (Note: DI generation requires a specific algorithm, and the results may vary depending on the service.)

When a user submits a passport and passes face authentication, ARGOS generates a unique DI value to represent that user.

This DI works like an encrypted user ID, and when the same DI is detected in another sign up attempt, ARGOS recognizes it as a duplicate user.

2. Strengthening Security at the Injection Stage

Security has been enhanced at the injection stage, where users begin inputting their information during the KYC process.
Using the user's IP address and location, the system automatically detects and blocks suspicious access attempts in advance.

• Block access via VPNs, proxies, or Tor browsers

• Set distance-based restrictions between users’ entered address and their actual location

• Allow KYC to begin only in specific countries or regions

This is especially effective for services where accurate address collection is critical.
It helps build a user friendly, fraud resistant authentication environment by blocking increasingly advanced overseas VPN and proxy users.

ARGOS also reinforces its IP based risk detection engine, enabling more advanced and intelligent user screening.

For example, if a user attempts to bypass verification using a VPN or proxy, and the distance between the entered address and actual IP location is significantly inconsistent, the system will automatically block the KYC attempt.

Additionally, the system can now automatically block access from blacklisted countries.
This feature isn’t exposed in the dashboard yet, but can be enabled via development settings by marking specific countries as “true” (restricted). It effectively prevents KYC attempts originating from those regions.

These detection features don’t stop at blocking suspicious users in real time they’re also useful after KYC is completed, for follow-up monitoring and risk analysis.

For example, on platforms like MapleStory Universe (MSU), where KYC is typically performed only once, ARGOS uses IP-based risk signals post-certification to assess user trustworthiness and determine whether further authentication is required.

In short, ARGOS offers a multi-layered defense system that improves:

• Security against suspicious access attempts

• Convenience for legitimate users

• Flexibility for detecting and managing suspicious behavior

ARGOS ensures the authentication process is secure, smart, and user-centered.

3. Improved WebHook Trigger

WebHook is a feature that automatically connects authentication results with external systems. What’s new? We’ve added more precise trigger conditions to enable smarter follow-up actions.

• Created: Automatically triggered when a user starts the authentication submission

• Retry: Triggered when the authentication process fails and requires a retry

• If authentication fails, the system now automatically marks the status as “Rejected.”

When using WebHook, you can receive real-time notifications through tools like Slack or email, and fully automate follow-up tasks such as contract processing, reward distribution, and user approval. Additionally, the GET /submission API response now includes submission environment history, enabling detailed tracking of the authentication attempt environment.

With this update, the WebHook feature becomes even more powerful. Previously, WebHooks only provided results such as ‘Approved,’ ‘Rejected,’ or ‘Pending.’ Now, you can also receive instant alerts when suspicious documents like forged IDs are detected. That means you’ll be notified about key events in the certification process, including KYC Start and Retry.

Even when automatic verification fails or the user is rejected right away, the result is sent through WebHook. This enables developers to monitor the authentication flow in real time without needing to check status updates manually.

By registering the WebHook just once in a project, you can immediately track how each authentication is progressing and identify any problems as they happen.

Another new feature is the Return URL Enhancement. Previously, after users completed KYC, they were redirected to a set return URL after a short delay but the result (Approved, Rejected, etc.) was not included. Developers had to manually check via the API or WebHook to retrieve it.

Now, the return URL directly includes the result status. Developers can access the essential outcome immediately, without needing to call additional systems.

This improvement significantly enhances developer convenience and supports better user flow after authentication for example, directing users to the next step upon approval, or showing a guide page if authentication is denied.

Through this update, ARGOS is evolving beyond a simple authentication tool into an intelligent, real-time decision-making platform. If you’re looking to automate the entire user verification process with a single setting, explore the enhanced WebHook and Return URL features today.

These May updates were designed not only to strengthen security but also to improve the overall user experience and trust in authentication-based services.

By proactively blocking fraudulent users, reducing unnecessary operational costs, and helping real users onboard faster this is the mission of ARGOS ID check.

We’re turning authentication into a competitive customer experience, not a barrier.
Experience the latest features now in the ARGOS dashboard!