Register a Legal Payer or Owner (with SCA enrollment)
UserCategory is OWNER, this endpoint triggers SCA enrollment.Your platform needs to use the returned PendingUserAction.RedirectUrl (and add an encoded returnUrl query parameter) to redirect the user so they can enroll. Read more about how to redirect them in the SCA session guide.SCA applies to all LegalPersonType: BUSINESS, ORGANIZATION, PARTNERSHIP, and SOLETRADER. In Sandbox by default the RedirectUrl is only returned for SOLETRADER (see legal user integration and SCA triggers in Sandbox).UserCategory is OWNER, the LegalRepresentative.Email address is required.SCA uses this email address for the individual who will complete SCA to build a behavioral biometrics profile and as a backup communication channel. Prior to SCA, it was possible to create a Legal OWNER without the LegalRepresentativeEmail.HeadquartersAddress.CountryLegalRepresentative.NationalityLegalRepresentative.CountryOfResidenceLegalRepresentativeAddress.CountryName value should be the one registered with the relevant national authority.LegalPersonType to use for a particular local legal structure, see the verification requirements.Caution: Modification of the LegalPersonType may result in a verification downgrade.UserCategory is OWNER and LegalPersonType is BUSINESS. Returned null if UserCategory is PAYER.The registration number of the entity, assigned by the relevant national authority. For information on the expected format for a specific country, see the Company number guide. To validate the format of a number before submitting documents for verification, use POST Validate the format of User data.UserCategory is OWNER. Child parameters returned null if UserCategory is PAYER.The legally registered address of the entity’s administrative center.true if UserCategory is OWNER.PAYER, OWNERThe category of the user:PAYER – User who can only make pay-ins to their wallets and transfers to other wallets (as well as refunds for pay-ins and transfers).OWNER – User who can also receive transfers to their wallets. Owners are able to request KYC verification, which if successful gives them the KYCLevel of REGULAR and the ability to request payouts.USER_PRESENT, USER_NOT_PRESENTDefault value: USER_PRESENTThe SCA context of the request, which is required if the OWNER value is being assigned for UserCategory:USER_PRESENT – The user is on session during OWNER account creation and can enroll in SCA at the same time. The platform must redirect the user using the PendingUserAction.RedirectUrl returned so that the user can complete the SCA session.USER_NOT_PRESENT – The platform has explicit permission from Mangopay to create the OWNER user account without simultaneous SCA enrollment.ScaContext is not returned in the API response as it does not form part of the User data – it’s only related to the action being performed on the user.200
Name value should be the one registered with the relevant national authority.LegalPersonType to use for a particular local legal structure, see the verification requirements.Caution: Modification of the LegalPersonType may result in a verification downgrade.Id of the KYC Document whose Type is REGISTRATION_PROOF if validated for the user. If no registration proof is validated, then this value is null.Id of the KYC Document whose Type is SHAREHOLDERS_DECLARATION if validated for the user. If no Shareholder Declaration is validated, then this value is null.Id of the KYC Document whose Type is ARTICLES_OF_ASSOCIATION if validated for the user. If no articles of association document is validated, then this value is null.UserCategory is OWNER and LegalPersonType is BUSINESS. Returned null if UserCategory is PAYER.The registration number of the entity, assigned by the relevant national authority. For information on the expected format for a specific country, see the Company number guide. To validate the format of a number before submitting documents for verification, use POST Validate the format of User data.null).null if the UserCategory is PAYER.NATURAL – Natural users are individuals (natural persons).LEGAL – Legal users are legal entities (legal persons) like companies, non-profits, and sole proprietors.PersonType is defined by the endpoint used to create the user and can’t be modified.LIGHTReturned values: LIGHT, REGULARThe verification status of the user set by Mangopay:LIGHT – Unverified, assigned by default to all users.REGULAR – Verified, meaning the user has successfully completed the verification process and had the necessary documents validated by Mangopay. Only users whose UserCategory is OWNER can submit verification documents for validation. Only users whose KYCLevel is REGULAR can request payouts.true if UserCategory is OWNER.TermsAndConditionsAccepted value was set to true.Returned null if UserCategory is PAYER.PAYER, OWNER, PLATFORMThe category of the user:PAYER – User who can only make pay-ins to their wallets and transfers to other wallets (as well as refunds for pay-ins and transfers).OWNER – User who can also receive transfers to their wallets. Owners are able to request KYC verification, which if successful gives them the KYCLevel of REGULAR and the ability to request payouts.PLATFORM – Single specific user that represents the platform. The PLATFORM value is only assigned by Mangopay and may be used as part of the validated workflow implemented by the platform.PENDING_USER_ACTION, ACTIVE, CLOSEDThe status of the user:PENDING_USER_ACTION – The user must enroll in SCA before they can become ACTIVE.ACTIVE – The user account is active and the user can access Mangopay features.CLOSED – The user account is permanently closed. This value is used by Mangopay to close an account following the procedure outlined in the terms and conditions.400 - First name or last name identified as fake
400 - Restricted country
400 - Invalid email
400 - LegalRepresentative.Email required if OWNER
403 - TermsAndConditionsAccepted must be true if OWNER