Sub-account Verification Result Notification

{
  "bizType": "INSTITUTION",
  "bizId": "2060249001916727298",
  "bizStatus": "PASSED",
  "clientId": "caoLHPyfvjtnJPJe",
  "data": "{\"subAccountId\":\"53695180\",\"authStatus\":\"PASSED\",\"accountType\":\"KYB\",\"auditTime\":1780036714339,\"rejectReason\":null}"
}

{
  "returnCode": "SUCCESS",
  "returnMessage": null
}

WEBHOOK

institutionVerifyResultWebhook

{
  "bizType": "INSTITUTION",
  "bizId": "2060249001916727298",
  "bizStatus": "PASSED",
  "clientId": "caoLHPyfvjtnJPJe",
  "data": "{\"subAccountId\":\"53695180\",\"authStatus\":\"PASSED\",\"accountType\":\"KYB\",\"auditTime\":1780036714339,\"rejectReason\":null}"
}

{
  "returnCode": "SUCCESS",
  "returnMessage": null
}

Overview

This page documents webhook institutionVerifyResultWebhook. Parameters, response schema, and examples are rendered from the linked OpenAPI definition above. When sub-account KYB verification completes (passed or rejected), GatePay sends a POST request to the callback URL configured by the merchant. The merchant should receive and parse the notification at that URL and return HTTP 200 to acknowledge receipt.

Notes

Use bizId for idempotency.
Signature verification, retries, parsing data, and the success response are covered in Notifications Overview; see Security and Signature for signing rules.

Trigger scenarios

Triggered when KYB verification completes after a sub-account submits verification and the status becomes passed or rejected
GatePay sends the notification to the merchant’s configured callback URL
If delivery fails, see retry rules in Notifications Overview

Message Structure

Field	Type	Description
`bizType`	string	Notification type; INSTITUTION = institution notification
`bizId`	string	Notification business ID
`bizStatus`	string	Business status: PASSED = verification passed, FAILED = verification rejected
`clientId`	string	Institution merchant client_id
`data`	string	Message content as a JSON string

Parsed `data` Content

Field	Type	Description
`subAccountId`	string	Sub-account ID
`authStatus`	string	Verification result: PASSED = passed, FAILED = rejected
`accountType`	string	Verification type; always `KYB`
`auditTime`	int64	Audit completion time (milliseconds)
`rejectReason`	string	Rejection reason; empty when passed

Callback examples

Verification passed:

{
  "bizType": "INSTITUTION",
  "bizId": "2060249001916727298",
  "bizStatus": "PASSED",
  "clientId": "caoLHPyfvjtnJPJe",
  "data": "{\"subAccountId\":\"53695180\",\"authStatus\":\"PASSED\",\"accountType\":\"KYB\",\"auditTime\":1780036714339,\"rejectReason\":null}"
}

Parsed content of data:

{
  "subAccountId": "53695180",
  "authStatus": "PASSED",
  "accountType": "KYB",
  "auditTime": 1780036714339,
  "rejectReason": null
}

Verification rejected

{
  "bizType": "INSTITUTION",
  "bizId": "2060249001916727299",
  "bizStatus": "FAILED",
  "clientId": "caoLHPyfvjtnJPJe",
  "data": "{\"subAccountId\":\"53695180\",\"authStatus\":\"FAILED\",\"accountType\":\"KYB\",\"auditTime\":1780036714339,\"rejectReason\":\"ID photo is unclear\"}"
}

Body

application/json

Sub-account verification result callback notification body

bizType

string

required

Notification type; INSTITUTION = institution notification

bizId

string

required

Notification business ID

bizStatus

string

required

Business status: PASSED = verification passed, FAILED = verification rejected

clientId

string

required

Institution merchant client_id

data

string

required

Message content as a JSON string; see InstitutionVerifyResultCallbackData after parsing.

Response

200 - application/json

Return HTTP 200 to acknowledge receipt.

Merchant acknowledgement returned after receiving the callback.

returnCode

string

required

Return status code, for example SUCCESS.

returnMessage

string | null

Return message.

Sub-account Creation Result Notification

Address Payment Status Notification

⌘I

Common

Balance

Institution

Payment

OTC

Convert

Payout

Gift Card

Subscription

Reconciliation

Notifications

Sub-account Verification Result Notification

Overview

Notes

Trigger scenarios

Message Structure

Parsed `data` Content

Callback examples

Verification rejected

Body

Response

​Overview

​Notes

​Trigger scenarios

​Message Structure

​Parsed data Content

​Callback examples

​Verification rejected

Body

Response

Overview

Notes

Trigger scenarios

Message Structure

Parsed `data` Content

Callback examples

Verification rejected