> ## Documentation Index
> Fetch the complete documentation index at: https://cobo.com/payments/llms.txt
> Use this file to discover all available pages before exploring further.

# KYC requirements by country

A paying entity must pass KYC review before it can create a POBO payout. The field names in [Submit merchant KYC](/payments/en/api-references/payment/submit-merchant-kyc) are the same in every supported country and region; only three things change with the entity's location: which attachment types (`file_type`) are required, which primary identity documents are accepted, and how Hong Kong addresses are validated.

This guide lists those three differences for Hong Kong SAR (`HKG`), Taiwan, China (`TWN`), Malaysia (`MYS`), Philippines (`PHL`), Indonesia (`IDN`), Vietnam (`VNM`), Thailand (`THA`), Singapore (`SGP`), United Kingdom (`GBR`), Mexico (`MEX`).

## Before you begin

* Prepare the paying entity's company documents or individual identity documents before you submit KYC information.
* Upload each required file with [Upload file v2](/payments/en/api-references/payment/upload-file-v2) and use the returned `file_id` values in the KYC request.
* Submit KYC information with [Submit merchant KYC](/payments/en/api-references/payment/submit-merchant-kyc).
* For the end-to-end POBO sequence, see [Payouts on behalf of (POBO)](/payments/en/guides/pobo).

## Shared request structure

The KYC request uses consistent JSON keys for all supported countries. Country-specific requirements change the accepted values and required attachments, not the field names.

| Scope | Fields |
| - | - |
| Top-level company request | `merchant_type`, `country`, `merchant_id`, `industry`, `company_info` |
| Top-level individual request | `merchant_type`, `country`, `merchant_id`, `industry`, `individual_info` |
| Address objects | `country`, `state`, `city`, `postcode`, `line1` |
| Person information | `name`, `name_en`, `id_number`, `date_of_birth`, `issue_date`, `expiration_date`, `residential_address`, `attachments` |

## Company KYC requirements

For company KYC, set `merchant_type` to `B2B` and provide `company_info`. Do not provide `individual_info` in the same request.

### HKG baseline fields

| Field | Requirement |
| - | - |
| `company_type` | Required. Use `Limited Company`. |
| `listed` | Required. Indicates whether the company is listed. |
| `identify_no` | Required. Company registration or identification number. |
| `company_name` | Required. Local company name. |
| `company_name_en` | Required. English company name. |
| `establish_date` | Required. Company establishment date in `YYYYMMDD` format. |
| `commencement_date` | Required. Business commencement date in `YYYYMMDD` format. |
| `valid_period` | Required. Validity date in `YYYYMMDD` format. |
| `operation_address` | Required. Includes `country`, `state`, `city`, `postcode`, and `line1`. |
| `register_address` | Required. Includes `country`, `state`, `city`, `postcode`, and `line1`. |
| `legal_info` | Required. Uses the PersonInfo structure for the legal representative. |
| `ubo_infos` | Required. Includes at least one UBO PersonInfo object. |
| `online_store_url` | Required unless a business document is provided instead. |
| `attachments` | Required. Includes company attachments. |

### Company attachment requirements

The `file_type` values below are what the operation accepts. Passing validation does not guarantee that compliance review approves the submission.

| Country | Company attachment `file_type` values | Legal representative and UBO primary identity document | Special rule |
| - | - | - | - |
| Hong Kong SAR (`HKG`) | `CI`, `BR`, `NNC1`, `AOA`, `ANNUAL_RETURN`, `BAP`, `SSC` | `FIC` | Baseline country. |
| Taiwan, China (`TWN`) | `CI`, `AOA`, `ANNUAL_RETURN`, `BAP`, `SSC` | `PP` | The request fields stay the same as `HKG`; omit `BR` and `NNC1`. |
| Malaysia (`MYS`) | `CI`, `AOA`, `ANNUAL_RETURN`, `BAP`, `SSC` | `PP` | The request fields stay the same as `HKG`; omit `BR` and `NNC1`. |
| Philippines (`PHL`) | `CI`, `AOA`, `ANNUAL_RETURN`, `BAP`, `SSC` | `PP` | The request fields stay the same as `HKG`; omit `BR` and `NNC1`. |
| Indonesia (`IDN`) | `CI`, `AOA`, `ANNUAL_RETURN`, `BAP`, `SSC` | `PP` | The request fields stay the same as `HKG`; omit `BR` and `NNC1`. |
| Vietnam (`VNM`) | `CI`, `AOA`, `ANNUAL_RETURN`, `BAP`, `SSC` | `PP` | The request fields stay the same as `HKG`; omit `BR` and `NNC1`. |
| Thailand (`THA`) | `CI`, `AOA`, `ANNUAL_RETURN`, `BAP`, `SSC` | `PP` | The request fields stay the same as `HKG`; omit `BR` and `NNC1`. |
| Singapore (`SGP`) | `CI`, `AOA`, `ANNUAL_RETURN`, `BAP`, `SSC` | `PP` | `company_name_en` must include the `Pte Ltd` suffix. |
| United Kingdom (`GBR`) | `CI`, `AOA`, `ANNUAL_RETURN`, `BAP`, `SSC` | `PP` | The request fields stay the same as `HKG`; omit `BR` and `NNC1`. |
| Mexico (`MEX`) | `CI`, `AOA`, `ANNUAL_RETURN`, `BAP`, `SSC` | `PP` | The request fields stay the same as `HKG`; omit `BR` and `NNC1`. |

For non-mainland China personnel, include `name`, `name_en`, `id_number`, `date_of_birth`, `issue_date`, `expiration_date`, `residential_address`, and `attachments`. For a mainland China identity card, the two sides are `PRC_ID_Emblem` and `PRC_ID_Portrait`.

## Individual KYC requirements

For individual KYC, set `merchant_type` to `B2C` and provide `individual_info`.

### HKG baseline fields

| Field | Requirement |
| - | - |
| `name` | Required. Local-language individual name. |
| `name_en` | Required. English individual name. |
| `id_number` | Required. Identity document number. |
| `date_of_birth` | Required. Date of birth in `YYYYMMDD` format. |
| `issue_date` | Required. Identity document issue date in `YYYYMMDD` format. |
| `expiration_date` | Required. Identity document expiration date in `YYYYMMDD` format. Use `20991231` for a document that is valid indefinitely and carries no printed expiry date. |
| `residential_address` | Required. Includes `country`, `state`, `city`, `postcode`, and `line1`. For `HKG`, `city` must use a supported Hong Kong district value. |
| `attachments` | Required. Includes both sides of the primary identity document, `ID_Hand`, and `POA`. Use the document's own `file_type` for the front and `BACK` for the reverse. |

### Individual country differences

| Country | Primary identity document `file_type` | Name language | `city` validation | Additional required attachments |
| - | - | - | - | - |
| Hong Kong SAR (`HKG`) | `HK_PID` or `FIC`; do not use `PP` for Hong Kong residents. | Chinese | Must use a supported Hong Kong district value in Chinese or English. | `ID_Hand`, `POA` |
| Philippines (`PHL`) | `FIC`; `PP` is also accepted. Do not use `HK_PID`. | English | Use the local English city name. | `ID_Hand`, `POA` |
| Taiwan, China (`TWN`), Malaysia (`MYS`), Indonesia (`IDN`), Vietnam (`VNM`), Thailand (`THA`), Singapore (`SGP`), United Kingdom (`GBR`), Mexico (`MEX`) | `PP`; `FIC` is also accepted. Do not use `HK_PID`. | English | Use the local English city name. | `ID_Hand`, `POA` |

## Hong Kong address requirements

For `HKG` individual KYC, `residential_address.city` must be one of the following values.

| Chinese value | English value |
| - | - |
| `中西区` | `Central and Western District` |
| `湾仔区` | `Wan Chai District` |
| `东区` | `Eastern District` |
| `南区` | `Southern District` |
| `油尖旺区` | `Yau Tsim Mong District` |
| `深水埗区` | `Sham Shui Po District` |
| `九龙城区` | `Kowloon City District` |
| `黄大仙区` | `Wong Tai Sin District` |
| `观塘区` | `Kwun Tong District` |
| `北区` | `North District` |
| `大埔区` | `Tai Po District` |
| `沙田区` | `Sha Tin District` |
| `西贡区` | `Sai Kung District` |
| `荃湾区` | `Tsuen Wan District` |
| `屯门区` | `Tuen Mun District` |
| `元朗区` | `Yuen Long District` |
| `葵青区` | `Kwai Tsing District` |
| `离岛区` | `Islands District` |

## Next steps

After the paying entity passes KYC review, create the recipient bank-account destination. For country-specific SWIFT requirements, see [Bank account requirements by country](/payments/en/guides/bank-account-requirements-by-country).