KYC
Last updated
Was this helpful?
Last updated
Was this helpful?
ARGOS supports various administrator accesses. Please add the administrator's email under Settings → General→ Access Management and save it. The added administrator can access the specific project automatically by logging in with the same email.
ARGOS provides the ability to control access based on IP addresses. Separate IP addresses can be specified for dashboard access and API access, and changes can be made in the 'Setting' tab of the dashboard.
Notification emails are sent when eKYC is approved, rejected, or completed (Pending). If you wish to receive the same emails sent to users as BCC (Blind Carbon Copy), you can use the BCC email reception option.
The eKYC status in ARGOS represents the final result of the user's eKYC process and is divided into four categories:
Approved (APPROVED): The status is given when the user's eKYC process successfully fulfills all the procedures set by the project manager. It means all requirements have been met.
Incomplete (INCOMPLETE): Refers to when the user's eKYC process has not yet been fully completed.
Rejected (REJECTED): The case where the eKYC process was rejected for not meeting the criteria set by the project owner. In this situation, the user must restart the eKYC process from the beginning.
Pending (PENDING): When ARGOS's AI system cannot process the final result, an AGENT manually reviews it. AGENTS are available 24/7 to handle pending eKYC statuses.
ARGOS allows a total of 3 retry opportunities for each submission. If a failure occurs during the process, it is treated as a Retry, and you can try again consecutively. In this case, the eKYC remains incomplete, indicating that it has not yet been completed.
*Incomplete cases with retry history are rejected for security after 72 hours.
Individual users can submit multiple eKYCs by creating 'multiple emails.' ARGOS provides the following features to prevent such users, supporting the 'one person, one account' principle:
Reject Duplicate User: Rejects if the identity information obtained as the final result of eKYC already exists. This prevents the same user from getting approved through multiple emails.
Approved period: Prevents interim submissions for approved users. This process prevents submissions using email, IP address, and identity information claimed by the user before the final identity verification. (*Since this method prevents submissions midway, it is impossible to verify the user's identity authentication result.)
ARGOS's eKYC allows 3 retries during a single submission, and the user must complete the entire authentication within these retries. Without limitations in the eKYC process, fraudsters or counterfeit users could find ways to pass individual stages through reverse engineering. To prevent such counterfeit users, ARGOS limits the number of retries in the eKYC process.
ARGOS's eKYC can be rejected for various reasons. 'Others' occur when the AGENT manually rejects it during the manual review stage after PENDING. It occurs when identity information cannot be visually confirmed or in cases not technically predefined.
The ARGOS Score is designed to prevent user dropout and support accurate and fast user onboarding by comprehensively analyzing the images and text information submitted by the user and calculating a reliability score.
High score: Causes more PENDINGS, leading to AGENT reviews.
Low score: Causes more automatic approvals. (*Submissions with a SCORE higher than the threshold are automatically approved.) → Automatically approved cases can be classified by score and reprocessed through post-review for possible Typos.
Customers can receive information at specific critical points during eKYC progress from ARGOS through webhooks.
Settings → General→ Access Management -> Enter the address to receive the webhook in the webhook URL and save it.
The easiest way to match customer's user databases with ARGOS's eKYC system is to use the userId. This userId can be found in Webhook and Get/Submission, allowing you to match it with your user database.
In the services provided by ARGOS, there are two types of data: text data and image data.
Text data: Personal information stored in the server through ARGOS is encrypted with AES-256. Additional encryption using the SecretKey on the client side is performed, so ARGOS Identity administrators cannot view the information in plaintext even if they access the database.
Image data: The image files you submit are protected with AES-256 encryption technology from the moment they are stored on the server. They are securely stored through AES-256 encryption executed in AWS S3 and KMS.
Users with dashboard access can grant access to others. This can be added or removed in the 'Setting' tab of the dashboard. If no one has access, please request it through the .
For more cases of rejection, please check .
Please refer for a detailed guide. It can be set under Settings→ User policy → ARGOS SCORE THRESHOLD. Test your submissions to see what ARGOS SCORE you should use for your eKYC policy. The initial setting value is 70.
Please check for detailed information on webhooks.
Liveform: You can include userId in the Query string used when calling Liveform. Please check for detailed setting methods.
API: You can include userId in the Option data when using the API. Please check for detailed setting methods.