Argos KYC
KYC Developer Guide
This starting guide explains how to establish a KYC process, process personal information, proper API use by KYC operation, submit KYC and call KYC results and AML results through API.

1. Introduction

To submit KYC, you should establish a KYC submission process.
You must first decide how to make KYC submissions(Liveform/API) and set project options.
KYC basically submits personal identity information, including ID photos and face photos, and automatically or manually inspects KYC based on the submitted information to approve or reject KYC.
KYC approval means "Identity was verified based on the submitted information," and KYC rejection means " Identity was not verified due to insufficient or incorrect information submitted".
If additional AML screening is required (project setting option), AML screening is automatically performed only for approved KYC submissions to provide AML search results. KYC approval does not mean "no risk as a result of AML search."
When the KYC is submitted, Argos KYC will perform the inspection automatically or manually. Therefore, the timing of receiving KYC results may be different.
In the case of auto-inspection, you will receive the KYC result through API response immediately after submission, and in the case of manual inspection, you can receive the KYC result event through webbook after manual inspection.

2. Submit KYC

There are two ways of submitting KYC, API or Liveform.
When using Liveform, submitters submit KYC through Argos form.
For API, you have to collect user's information, deliver the data to Argos KYC with API from the server.

Submission method 1: Liveform

Each project generates a unique form URL. Form URL can be found in the administrator system.
Argos form is made on the web, but you must obtain camera rights for ID and face capture. Therefore, it is basically designed to submit in a mobile environment, and when you open a form URL with a PC or desktop, a QR code for switching to mobile will be displayed on the screen.
Modification of the form is available with some limitations. For modifiable form options, refer to the project setting option document.
Submitter's email, User ID, or custom value can be submitted to the URL parameter together. Refer to the Liveform Guide to check how to submit custom values.

Submission method 2: API

API keys can be found in the administrator system.
KYC submission through API is divided into two APIs. Therefore, in order to complete the KYC submission, two different APIs must be called and submitted sequentially. Step 1, First API is the submission of ID card image, and Step 2, the second API is the submission of selfie image to complete KYC submission. If the KYC submission is not completed properly, the submission will be terminated without KYC being inspected as "incomplete".
If the KYC is submitted normally, an automatic inspection will be performed at Argos KYC, and if the automatic inspection is completed, the results of the KYC "approval" or "rejection" can be received as API response immediately after the submission is completed.


Submit your ID card in Step 1. (Refer to the API Guide)
curl -X POST "" \
-H "x-api-key: {yourAPIKey}" \
-d ...
The purpose of step 1 is to extract identity information from ID card.
In order to extract ID information properly from the ID card image, the country where the ID card is issued, and the type of ID card values are essential.
The API response in Step 1 generates and returns the essential value of Step 2 'submission_id' along with the information extracted from the ID card.


Submit your face image in Step 2. (Refer to the API Guide)
curl -X POST "" \
-H "x-api-key: {yourAPIKey}" \
-d ...
The purpose of submitting a face image in Step 2 is to compare it with the face on the ID card submitted in Step 1 to confirm that it is the real owner of the ID card.
Additionally, in Step 2, the identity information of the submitter acquired from response in Step 1 must also be submitted as input. It can be modified by the submitter and submitted in Step 2 if the information on the ID card was not accurately extracted through the OCR in Step 1.
In other words, the identity information automatically extracted from the step 1 is a convenience function that helps the submitter check the input value without entering it directly. The KYC inspection is practically performed based on the information submitted in step 2.
In order to submit an image of the user's face that matches the ID card submitted in Step 1, the 'submission_id' received in response from step 1 must be included as an essential value.
If step 2 is submitted properly, the KYC submission will be completed. If the automatic inspection is completed immediately after submission, you can receive immediate approval or rejection results through step 2 response.
Submissions required for manual inspection will be returned as 'pending', and the pending case will be finally approved or rejected after being reviewed manually by Argos' inspector.
For the results of the manual inspection, you can receive the results in real-time as soon as the inspection is completed by setting up the webbook.
For webbook settings, please refer to the project setting option document.
There are cases where a retry request is received with the result of 'incomplete' in response from step 2.
  1. 1.
    If there is no "face" in the selfie image
  2. 2.
    If there are more than two "faces" in the selfie image
  3. 3.
    If the face image is different from the face in the ID card (the face comparison score is less than 85 points)
  4. 4.
    When it is determined that the face image has been stolen or forged(less than 50 points of the liveness score)
  5. 5.
    (Korean ID cards only)Where verification of authenticity fails
If step 2 is incomplete, you only need to check the reason and resubmit the step 2. Restarting from step 1 will be treated as a new KYC submission, and a new submission id will be issued, and additional costs may be incurred.
Retying of Step 2 is allowed three times at max, and if you do not receive the result of either ‘approved’ or ‘pending’ in the third attempt, the "rejected" will be returned and the submission will be rejected.
If KYC is rejected, you have to restart the new KYC from step 1.

3. Check KYC Information

Information on KYC submissions can be checked by registering to the dashboard provided by Argos KYC, or you can call API to check KYC data.

Check from administrator system(Dashboard)

Argos KYC Dashboard:
You have to first sign up to the dashboard and apply for permission through HELPDESK.

Get KYC information by API

You can call information on submission using API. (Refer to the API Guide)
curl -X GET "{submission_id}"\
-H "x-api-key: {yourAPIKey}"
The information called to the API includes the submitter's information, KYC-related information, and AML information.
The Submission ID inquired can be checked by the following methods.
  1. 1.
    Call the submission list to check the submission id in the entire submission list.
  2. 2.
    At the time of completion of submission or inspection, receive and confirm the submission ID using webhook.
  3. 3.
    Log in to the dashboard and check the submission details.

4. Delete Submission

Since KYC handles the submitter's personal information, it is necessary to establish a policy for processing and storing personal information.
Argos KYC first stores KYC information for inspection purposes. After the KYC inspection, you have to decide whether to store the information directly, not in Agros KYC database anymore.
You can keep the submissions at Argos KYC even after the inspection is completed. Archived submissions can be viewed through the dashboard or API.
If you want to keep personal information and KYC information of the inspected submissions, get and save the submission by API, and will be deleted from Argos KYC database after the save is completed.
If the submission is deleted, the submission, including personal information, will be completely deleted from the Argos server, and cannot be restored. Additionally, information on the submission cannot be checked on the dashboard, and only the deletion event log can be recorded to confirm that it has been deleted.
curl -X DELETE "{submission_id}"ㅁcurl -X DELETE "{submission_id}"
Last modified 9d ago