Submit KYC Documents

POST 
/api/v2/client/:clientid/customer/:customerid/kyc/:kycid/documents

Uploads identity and supporting documents against a KYC submitted through Submit Customer KYC.

US flow only. On the Standard flow, documents are sent inline on the KYC submission and every request here is rejected with 400 INVALID_PARAMETERS.

Requirements:

• kycid must come from the KYC submission response and must belong to customerid, which must be linked to your clientid. A mismatch returns 403; an id that does not exist returns 500.
• The KYC must be in initiated, in_review, rfi_requested, edd_initiated or edd_in_review. active and failed cannot accept documents.
• Documents are processed in array order and processing stops at the first rejection. The response does not name the failing entry, and nothing is attached when a request fails.

A 200 means the documents were accepted against the KYC record. Submission for verification is asynchronous, so it does not confirm that verification accepted them — track progress through Get Customer KYC Status and the RFI APIs.

Request

Responses

200

Documents accepted against the KYC record.

400

The request was rejected. INVALID_PARAMETERS covers an empty documents array, a missing document_type, an empty file, a KYC that is not in an upload-eligible status, a KYC whose submission did not complete, and every Standard-flow request.

401

MISSING_TOKEN when the X-ROMA-Signature header is absent, INVALID_TOKEN when it matches no active credential.

403

The customer is not linked to this clientid, the customer is unknown, or the KYC record does not belong to the customer.

500

The kycid does not exist, the body is not valid JSON, or the upload could not be completed. An unknown kycid is reported here rather than as 403 or 404.