# Merchant KYC Profiling

## Elements of KYC Profiling

The following are some of the components of KYC profiling;-

**Introduction & Purpose:** This is an introductory part of the KYC that explains the importance of KYC profiling in ensuring security and regulatory compliance. It also states the purpose of the KYC process for GovNet.

**Compliance with Regulations:** This section has information on how the KYC process complies with relevant laws and regulations, such as Anti-Money Laundering (AML) and Counter-Terrorism Financing (CTF) laws that the GovNet gateway should also comply with.

**Data Privacy:** This contains information on how merchant/ customer data is protected and handled in accordance with data privacy laws while processing with GovNet gateway.

**Customer Due Diligence (CDD):** This describes information on the level of due diligence required for different Merchant types, such as government entities, or Private businesses that GovNet is meant to process traffic for.

**Merchant Validation and Verification:** This includes details on the types of documents required by the legal team, such as government-issued IDs, passports, driving permit, Certificate of registration from the registration bureau, memorandum of understanding for joint businesses, etc.

Therefore it is very important that the merchants the guidelines listed in the KYC documentation to ensure that they are compliant with relevant laws and regulations in any country of business operation.


---

# 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://productdoc.govbill.ug/merchant-onboarding/merchant-kyc-profiling.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.