List UBO Declarations for a User
Caution – Legacy endpoints being superseded by the hosted KYC/KYB solution
Mangopay’s hosted KYC/KYB solution is becoming mandatory for all platforms, and allows Legal Users to declare and verify all beneficial owners in the same IDV Session object.
The criteria defining beneficial owners remain the same.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.
Path parameters
Query parameters
Start value: 1
Default value: 1
Indicates the index of the page for the pagination.
Min. value: 1; max. value: 100
Default value: 10
Indicates the number of items returned for each page of the pagination.
Possible values: CreationDate:ASC, CreationDate:DESC
Default value: CreationDate:ASC
Indicates the direction in which to sort the list.
Response
Max length: 128 characters (see data formats for details)
The unique identifier of the object.
Unix timestamp (UTC) of the date and time the object was created.
Unix timestamp (UTC) of the date and time the UBO Declaration was processed by Mangopay’s team.
Returned values: CREATED, VALIDATION_ASKED, INCOMPLETE, VALIDATED, REFUSED
The status of the declaration:
CREATED– The UBO Declaration is created, but not submitted yet.VALIDATION_ASKED– The UBO Declaration is submitted for validation.INCOMPLETE– The UBO Declaration is deemed incomplete by Mangopay teams.VALIDATED– The UBO Declaration is validated by Mangopay’s team.REFUSED– The UBO Declaration is rejected by Mangopay’s team. You can learn more about the reasons for refusal in theReasonandMessagefields.
The reason for which the UBO Declaration was REFUSED or considered as INCOMPLETE.