Submit Partner KYC Verification

Submit pre-verified KYC screening results and document information from a partner platform. PayMongo verifies the screening data via the Verifications API and marks the account's identity verification as passed if validation succeeds.

The endpoint integrates with the Verifications API to validate the partner verification data. Document information and screening results are validated against PayMongo's compliance requirements.

This endpoint does not activate the account. After partner verification is submitted, you should populate additional person and business details via the Update Account endpoint, then activate the account separately.

Only the parent account can submit partner verification data for child accounts. The partner platform must be pre-approved and enabled by PayMongo for KYC Reliance.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
^org_[a-zA-Z0-9]+$

Unique identifier for the account

Body Params
risk_profile
object
required
documents
array of objects
required
length ≥ 1

Array of identity documents for verification (exactly 1 selfie required, plus 1 primary ID or 2+ secondary IDs)

documents*
string
enum
required

Type of document.

For selfie documents:

  • Exactly 1 selfie document required per request
  • Only front_image_url is used; id_number, back_image_url, and metadata are ignored
  • Used for liveness check and face matching

For ID documents (KYC):

  • id_number and metadata are required
  • Each document type must be unique (duplicates not allowed)
  • back_image_url required for: national_id_ph, driving_license_ph, alien_registration_card_ph, other_passport

For business documents (KYB - corporation/partnership):

  • Used for business verification in partner verification
  • Optional: id_number and metadata
  • Only front_image_url required
string

ID number or reference (not required for selfie)

uri
required

HTTPS URL to front image (for ID documents) or selfie photo. Required for all document types.

uri

HTTPS URL to back image of ID document (not used for selfie).
Required for: national_id_ph, driving_license_ph, alien_registration_card_ph, other_passport.
Optional for all other ID document types.

metadata
object

Document metadata with OCR fields. Not required for selfie documents.
For ID documents: at least 1 key-value pair required, with no empty values.

person
object

Person information to update from partner verification (optional; TIN required for merchants)

business
object

Business information (REQUIRED for merchant accounts, not allowed for consumers)

ubos
array of objects

Ultimate Beneficial Owners (REQUIRED for merchant accounts with min 1, not allowed for consumers)

ubos
Responses

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json