Add Business KYC Rejection and Resubmission Capabilities
Effective Date: 2026-07-31Scope: Business Onboarding / KYC
Introduced a dedicated business guide for KYC rejection and resubmission. This guide details how to query specific rejection reasons when a business entity's review is rejected (with value of kycStatus changed to 'request'). It explains how to precisely resubmit individual documents based on different business types through a new workflow, helping developers build a smoother compliance loop.
Introduced a new endpoint to query KYC rejection information. When a business entity's KYC status changes to 'request', developers can use this endpoint to retrieve the list of rejection details. By parsing the bizType field in the response, you can precisely identify the type of rejected content, and records with a status of 'pending' represent tasks that currently require resubmission.
Introduced a new endpoint to resubmit business basic information. This endpoint is specifically designed to handle rejection items where the bizType is BUSINESS_BASIC_INFO, allowing developers to resubmit the latest basic information or business qualification materials for the entity.
Introduced a new endpoint to resubmit related personnel information. This endpoint is specifically designed to handle rejection items where the bizType is HOLDER_INFO (e.g., directors, signers, or representatives) or BENEFICIAL_OWNER_INFO (ultimate beneficial owners), allowing developers to resubmit personal profiles and compliance documents for specific individuals.
Introduced a new endpoint to add personnel during the rejection period. This is used when compliance requires the addition of new personnel, allowing you to dynamically append related personnel records to the current business entity and generate an independent biometric authentication task.
Introduced a manual exception clearance endpoint for material-type tasks. This endpoint serves strictly as a fallback safety mechanism for extreme exception scenarios, used to manually force specific material-type pending records into a closed loop.
- It is strictly prohibited to use this endpoint for
FACE_BIOMETRICtasks; biometric tasks must be actually completed and verified by the designated person to be cleared.
Added the rejectionRecordId request parameter to the biometric URL creation endpoint. This update is specifically designed to support the facial rejection resubmission flow where the bizType is FACE_BIOMETRIC. By passing the corresponding rejection record ID, the system will correctly associate the newly generated authentication result with that pending task.
Thank you for choosing DogPay! If you encounter any issues or need assistance during integration, please feel free to reach out to the technical support team.