Creates a KYC Review for a specific customer action.
Optional UUID for correlating requests across systems. If provided, Wise echoes it back in the response. Maximum 36 characters. Learn more.
Type of the underlying action or process this KYC Review is for. Usually a reference to which product this KYC Review is for (like QUOTE or TRANSFER) or a reference to a KYC process on the profile that isn't related to a specific product (like REFRESH_CYCLE or REPAPERING).
Following types are available when creating a KYC Review using this endpoint:
QUOTEPROACTIVE_SEND_MONEYCARD
- Production Environmenthttps://api.wise.com/v1/profiles/{profileId}/kyc-reviews
- Sandbox Environmenthttps://api.wise-sandbox.com/v1/profiles/{profileId}/kyc-reviews
curl -i -X POST \
'https://api.wise.com/v1/profiles/{profileId}/kyc-reviews' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'X-External-Correlation-Id: f47ac10b-58cc-4372-a567-0e02b2c3d479' \
-d '{
"type": "QUOTE",
"triggerData": {
"id": "ba83a43a-f623-46f0-956d-196c13e2ab01"
}
}'KYC Review successfully created.
Echoed back when X-External-Correlation-Id was included in the request. Learn more.
Unique identifier for a KYC Review resource, generated by Wise.
Aggregated state of the underlying requirement set. Any of the states below could move into any other state.
Timestamp marking the creation of the KYC Review.
Timestamp marking the last update of the KYC Review.
Timestamp by which the underlying requirement set needs to be verified to not block the customer. Only relevant if the status is PASSED_WITH_REQUIREMENTS.
URL where the user will be redirected at the end of the flow. Can contain query params and path fragments. It has to be a valid URL as per RFC 2396. Provided by the caller in the Update redirect URL call.
Nested list of KYC Requirement objects in [[Requirement]] format, where each inner list represents a combination of possible requirements to be provided. To fulfil the whole KYC Review, at least one item from each inner list should be provided.
For example, if the requirements are [[a, b], [c, d]] then it should be read as (a or b) and (c or d).
{ "id": "46e1a5c4-4a9b-4563-39d3-18174d3ac0f8", "status": "WAITING_CUSTOMER_INPUT", "createdAt": "2024-09-03T16:22:02.257725", "updatedAt": "2024-09-03T16:29:41.147522", "requiredBy": "2024-09-03T16:22:02.257725", "triggerReferences": [ { "type": "QUOTE", "triggerData": { … } } ], "redirectUrl": "https://example.com", "requirements": [ [ { … } ] ] }