Submit a KYC requirement for a KYC Review.
- A KYC requirement can only be submitted if the KYC Review status is
WAITING_CUSTOMER_INPUTorPASSED_WITH_REQUIREMENTS. - A KYC requirement should only be submitted if its
stateisNOT_PROVIDEDandapiCollectionSupportedistrue.
The structure of submissionData depends on the requirementKey. If you already know which requirement type you are implementing, select it in the request body to see its fields and a matching request sample.
To explore which requirement types exist and what each one collects, see the KYC requirement types guide for the full list of supported requirement types, submission data structures, and accepted values.
The KYC requirement type to submit.
To see the fields for a requirement type, select it in the request body dropdown below. To compare all requirement types, see the KYC requirement types guide.
Optional UUID for correlating requests across systems. If provided, Wise echoes it back in the response. Maximum 36 characters. Learn more.
- Production Environmenthttps://api.wise.com/2027Q1/profiles/{profileId}/kyc-requirements/{requirementKey}
- Sandbox Environmenthttps://api.wise-sandbox.com/2027Q1/profiles/{profileId}/kyc-requirements/{requirementKey}
curl -i -X POST \
'https://api.wise.com/2027Q1/profiles/{profileId}/kyc-requirements/{requirementKey}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: multipart/form-data' \
-H 'X-External-Correlation-Id: f47ac10b-58cc-4372-a567-0e02b2c3d479' \
-d '{}'KYC requirement successfully submitted.
Echoed back when X-External-Correlation-Id was included in the request. Learn more.
No content