View a UBO Declaration

Authentication

AuthorizationBearer
Bearer authentication of the form `Bearer <token>`, where token is your auth token. If your platform is using a [proxy](/guides/sca/proxy-management) to take SCA-triggering action on behalf of users, you also need to integrate [mTLS authentication](/guides/sca/platform) and use the `api-mtls` base URL.

Path parameters

ClientIdstringRequired
Platform's API account identifier, associated with the API key.
UboDeclarationIdstringRequired
The unique identifier of the UBO Declaration.

Response

Success
Idstring

Max length: 128 characters (see data formats for details)

The unique identifier of the object.

UserIdstring
The unique identifier of the user.
CreationDateinteger

Unix timestamp (UTC) of the date and time the object was created.

ProcessedDateinteger

Unix timestamp (UTC) of the date and time the UBO Declaration was processed by Mangopay’s team.

Statusstring

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 the Reason and  Message fields.
Reasonstring

The reason for which the UBO Declaration was REFUSED or considered as INCOMPLETE.

Messagestring

Additional information about why the UBO Declaration was refused or marked as incomplete, provided by Mangopay’s team.

Uboslist of objects
The list of UBOs attached to the UBO Declaration.