The Legal User object (SCA)
The Legal User object (SCA)
Description
The Legal User object represents a legal entity (legal person) like a company, non-profit or sole proprietor (read more about user types).
Mangopay users have one of two categories, indicated by UserCategory:
PAYER– User who can only make pay-ins to their wallets and transfers to other wallets.OWNER– User who can also receive transfers to their wallets. Owners are able to request KYC verification, which if successful gives them theKYCLevelofREGULARand the ability to request payouts.
To enable OWNER users to enroll in SCA, Mangopay released new versions of the user objects and new endpoints.
Changes from non-SCA object
The changes to the Legal User object are:
- New
UserStatusvaluePENDING_USER_ACTIONindicating that the user must enroll in SCA - New response parameter
PendingUserAction.RedirectUrlcontaining the SCA session URL to which the individual must be redirected (after adding an encodedreturnUrlquery parameter) - New
LegalRepresentativeobject to group parameters related to the declared legal representative. This object includes the newLegalRepresentative.PhoneNumberandLegalRepresentative.PhoneNumberCountry, which may be used to pre-populate the user’s phone number in the SCA session
Caution – Legal representative’s email required
For OWNER users, the LegalRepresentative.Email address is required.
SCA uses this email address 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, so this data may be missing. Calling the POST Enroll a User in SCA endpoint without this data will return an error.
Attributes
Max. length: 255 characters
The registered legal name of the entity. The Name value should be the one registered with the relevant national authority.
Returned values: BUSINESS, PARTNERSHIP, ORGANIZATION, SOLETRADER
The type of legal user. For information on which LegalPersonType to use for a particular local legal structure, see the verification requirements.
Caution: Modification of the LegalPersonType may result in a verification downgrade.
The 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.
The 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.
Required if 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.
Object containing the RedirectUrl needed for SCA redirection if triggered by the API call (otherwise returned null).
The legally registered address of the entity’s administrative center.
This object’s sub-parameters are null if the UserCategory is PAYER.
The address of the entity’s legal representative.
Max length: 128 characters (see data formats for details)
The unique identifier of the object.
Max. length: 255 characters
Custom data that you can add to this object.
Unix timestamp (UTC) of the date and time the object was created.
Returned values: NATURAL, LEGAL
The type of the user:
NATURAL– Natural users are individuals (natural persons).LEGAL– Legal users are legal entities (legal persons) like companies, non-profits, and sole proprietors.
The PersonType is defined by the endpoint used to create the user and can’t be modified.
Format: A valid email address
The email address for the entity.
Default value: LIGHT
Returned values: LIGHT, REGULAR
The 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 whoseUserCategoryisOWNERcan submit verification documents for validation. Only users whoseKYCLevelisREGULARcan request payouts.
Whether the user has accepted Mangopay's terms and conditions (as defined by your contract, see the T&Cs guide for details).
Must be true if UserCategory is OWNER.
The date and time at which the TermsAndConditionsAccepted value was set to true.
Returned null if UserCategory is PAYER.
Possible values: PAYER, OWNER, PLATFORM
The 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 theKYCLevelofREGULARand the ability to request payouts.PLATFORM– Single specific user that represents the platform. ThePLATFORMvalue is only assigned by Mangopay and may be used as part of the validated workflow implemented by the platform.
Returned values: PENDING_USER_ACTION, ACTIVE, CLOSED
The status of the user:
PENDING_USER_ACTION– The user must enroll in SCA before they can becomeACTIVE.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.