Submit a UBO Declaration
Read more about the UBO Declaration object →
Submitting a UBO Declaration consists in updating the object Status
parameter value to VALIDATION_ASKED
.
From there, Mangopay Compliance team will validate, indicate as incomplete, or reject the declaration.
Path parameters
The unique identifier of the user.
The unique identifier of the UBO Declaration.
Body parameters
Allowed values: VALIDATION_ASKED
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 theReason
andMessage
fields.
Responses
200
200
Max length: 128 characters (see data formats for details)
The unique identifier of the object.
The unique identifier of the user.
The date and time at which the object was created.
The date and time at which 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 theReason
andMessage
fields.
The reason for which the UBO Declaration was REFUSED
or considered as INCOMPLETE
.
Additional information about why the UBO Declaration was refused or marked as incomplete, provided by Mangopay’s team.
The list of UBOs attached to the UBO Declaration.