Skip to main content
A paying entity must pass KYC review before it can create a POBO payout. The field names in 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 and use the returned file_id values in the KYC request.
  • Submit KYC information with Submit merchant KYC.
  • For the end-to-end POBO sequence, see Payouts on behalf of (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.

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

Company attachment requirements

The file_type values below are what the operation accepts. Passing validation does not guarantee that compliance review approves the submission. 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

Individual country differences

Hong Kong address requirements

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

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.