KYC General
At the dashboard - 'Setting' tab, API key and Liveform URL are displayed.
'Incomplete' means literally un-finished status. To complete a KYC, applicants need to submit ID image and face image sequentially. While submitting necessary data, when users stop to proceed, the submission remains as 'Incomplete' and it occurs in two main cases.
- 1.Only ID image submitted: Data required to process a KYC is not collected so it remains as 'Incomplete'.
- 2.Face image submitted but stopped at 'retry' process: When failed at face compare of liveness check, ARGOS provides 2 additional 'retry' chances. If a user leaves at this process, it also remains as 'Incomplete'. But data required to process a KYC is submitted so after about 24 hours, it turns to 'Rejected'.
KYC can be rejected automatically or manually, main reasons are as follows:
- 1.Multiple invalid KYC attempts: When failed at face confirmation. (Different face, face not detected, Liveness check fail etc..)
- 2.KYC rejected due to timeout: When 'Incomplete' submissions turn into 'Rejected'. *If KYC process is abandoned after the face confirmation process, the submission remains as 'Incomplete'.
- 3.Unacceptable ID type: When un-designated type of ID is submitted, the condition is set as project option(Passport, Driver's License, Government ID)
- 4.According to the policy, we do not accept KYC from {country}: When KYC is submitted with blacklist(follows project option) country issued ID.
- 5.We do not accept KYC anyone under {13} years old: When KYC is submitted by a user under the age limit(follows project option).
- 1.Fail to read the ID image: When ID image is not clear enough to read with naked eyes due to light smudging, ID damage, image quality etc...
- 2.Invalid ID document: When ID is not acceptable due to lack of information(name, date of birth), expiration, unsupported language etc...
- 3.ID document not detected: When an image of something else other than an ID is submitted.
- Face photo, full name, birth year and date: ID with only birth year, without month and day, will be rejected.
- Should be printed among Alphabet, 한글, 漢字, 日本語, Кириллица: Handwritten ID will be rejected.
- Must not be expired.
- Should be issued from the government: Employee ID cars, student cards are not acceptable.
- Characters should be recognizable.
- The image should be clear without light reflection or holographic reflection.
- ID image should have a little bit of padding.
Generally, we do not accept an ID as valid that is too old to compare face. When it is hard to compare a face with an ID, please guide users to try KYC with the latest ID card.
ID authentication checks the authenticity of South Korean Driver's license and government ID(Jumin-deunglogjeung) by combining ID info and personal info.
The collected information is compared to the government database. Through this procedure, ARGOS KYC clarifies whether the information is actually registered.
Authentication API service works as theft prevention of ID cards and personal information. This is because forged identities cannot find matching results in government databases.
Passed authenticity means "confirmed identity information of an existing person."
ARGOS KYC Athentication API service compares the ID information with the government database. We check if there is matching data with collected personal info and detect forged ID cards.
This is because if you tamper with someone else's ID card or create one that does not exist, you can not pass authentication since there's no matching information in the government database.
ARGOS KYC Athentication API service does not require additional development or software installation. You can simply get and post information with API and check the results within seconds.
ID Type | Data Source |
|---|---|
Government ID (Jumin-deunglogjeung) | |
Driver's license |
If you need to collect RRN(Resident Registration Numbers), first request to RRN through Helpdesk. If there is no request, ARGOS KYC does not collect resident registration numbers under the Personal Information Protection Act by default.
When resident registration numbers are not collected, it follows the following process.
If the resident registration number cannot be collected, the back 7 out of 13 resident registration numbers will be automatically masked.
*The first 6 digits correspond to the date of birth and cannot be masked.
The verification of the authenticity of the Korean resident registration card and driver's license must be accompanied by the collection of 13 digits of the resident registration number. If the resident registration number cannot be collected, the "skip" process will be applied to the authenticity check.
*If the "Skip" process is applied, authenticity verification does not affect KYC results.
The resident registration card is verified with the "fullName", "resident registration number" and "issuance date".
The resident registration number and issued date can be checked by step 1's response if the ID card is normally recognized in step 1.
If you submit the issuance date to date_of_issue and your resident registration number to the identity_number as input parameters in step2, you can receive the 'verificationResult' value as a response.
If 'verificationResult' indicates success, authenticity verification is successful, and if it indicates fail, it means there are either forgery or incorrect resident registration numbers.
If more than 5 ID check attempts are made on a single ID number, further ID checks on the same ID number are prohibited and locked until the ID owner unlocks it. Please make sure not to make too many invalid ID check requests.
When the account is locked, only the owner can unlock it.
ARGOS processes data deletion requests from the data subject(KYC submitter) based on GDPR(General Data Protection Regulation). The sequence is as follows:
- 1.ARGOS only accepts requests through the CS channel.
- 2.ARGOS will verify the user by email reply.
- 3.ARGOS will notify our clients(service providers) that the data of a specific person will be deleted.
- 4.A week after the notification, all personal information attributed to the email will be deleted.
Please contact us through the below channel for a request.
Last modified 2mo ago