# KYC Full

### Description:

This endpoint is tailored to facilitate a comprehensive Know Your Customer (KYC) verification by allowing users to upload their essential documents. A full KYC verification is imperative for enhanced security and regulatory compliance.

**Mode:**

`PUT`

#### Node:

```bash
/third-party-service/kyc/upload-document
```

<mark style="color:orange;">`PUT`</mark> `/third-party-service/kyc/upload-document`

Send user of wallet to undergo KYC lite and sign in/up.

#### Headers

| Name                                            | Type                                                                                                                                                 | Description                                                    |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| API-Key<mark style="color:red;">\*</mark>       | String                                                                                                                                               | Your API key for authentication.                               |
| API-Secret<mark style="color:red;">\*</mark>    | String                                                                                                                                               | Your API secret for enhanced security.                         |
| Authorization<mark style="color:red;">\*</mark> | eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6IkBub3ZhNDciLCJzdWIiOjExNywiaWF0IjoxNjg5MDk1MDI3fQ.0BHv\_jc6etSqAuTinoKxSiXnmrC4XLfiezRQZbNG8cA | Access token obtained from the KYC Lite process. Example token |

#### Request Body

| Name                                        | Type                             | Description                                                                                         |
| ------------------------------------------- | -------------------------------- | --------------------------------------------------------------------------------------------------- |
| Form-Data<mark style="color:red;">\*</mark> | idCardFront, idCardBack, selfie. | <p>value docType can be idCardFront, idCardBack, selfie. (Image below for reference)</p><p><br></p> |

{% tabs %}
{% tab title="202: Accepted " %}

<pre class="language-json"><code class="lang-json">// 
<strong>{
</strong>    "statusCode": 202,
    "message": "upload KYC full successful"
}
</code></pre>

{% endtab %}
{% endtabs %}

#### Form Data:

For KYC Full we need three documents. First parameter, would be idCardFront, then idCardBack, and finally a selfie of the individual to complete the full KYC process.

<figure><img src="/files/qReJDL0fApmhRC4aGvno" alt=""><figcaption><p>value docType can be idCardFront, idCardBack, selfie</p></figcaption></figure>

#### Considerations:

The end point must execute three once per type of document, the authorization is the access token and can get it from kyc lite /login-sof-kyc

The archive only accepts binary archives and does not accept buffers, base64, or anything other than a binary archive. Permitted archives include JPG and PNG. Value docType can be idCardFront, idCardBack, and selfie.&#x20;

Specific Information regarding KYC Documents by country can be found [here](/alfred-integration-docs/welcome/alfred-overview/required-documents-for-kyc-by-country.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alfred.gitbook.io/alfred-integration-docs/penny-api-general-integration/penny-api-operations/kyc-full.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.