Sign in

v2

latestOpenAPI 3.1.02026-07-262279731.3 MB
Users

Update a Natural User (SCA)

Modify details for a Natural Payer or Owner without changing category.

<Warning icon="fa-regular fa-triangle-exclamation"> **Caution – Modification may trigger SCA re-enrollment**

If UserCategory is OWNER, modifying the following values changes UserStatus to PENDING_USER_ACTION and requires re-enrollment in SCA using the returned PendingUserAction.RedirectUrl:

  • Email
  • PhoneNumber
  • PhoneNumberCountry

In Sandbox, you can bypass SCA by including the word accept in the Natural User's Email – for example accept@example.com or john.doe+accept@example.com. </Warning>

<Warning icon="fa-regular fa-triangle-exclamation"> **Caution – Modification may cause KYC/B verification downgrade**

If KYCLevel is REGULAR, modifying the following values triggers a verification downgrade to LIGHT:

  • FirstName
  • LastName
  • Birthday
  • Nationality </Warning>
<Note icon="fa-regular fa-circle-info"> **Note – Country-based restrictions apply to users**

Due to Mangopay's country restrictions, it is not possible to use blocked countries as the following:

  • Nationality
  • CountryOfResidence
  • Address.Country
</Note>
put/v2.01/{ClientId}/sca/users/natural/{UserId}

Path parameters

ClientIdstring required

Platform's API account identifier, associated with the API key.

UserIdstring required

Headers

Authorizationstring required

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.

Request body

OR

Response

Success

FirstNamestring

Min. length: 1; max. length: 100

The first name of the individual.

LastNamestring

Min. length: 1; max. length: 100

The last name of the individual.

Birthdayinteger nullable

Returned null if UserCategory is PAYER.

The date of birth of the individual.

Note: This is a Unix timestamp in UTC. Ensure you convert your timezone to UTC to avoid midnight being interpreted as the day before.

Nationalitystring nullable

Returned null if UserCategory is PAYER.

The nationality of the individual.

CountryOfResidencestring nullable

Returned null if UserCategory is PAYER.

The country of residence of the individual.

Occupationstring nullable

Max. length: 255 characters

The occupation of the individual.

Returned null if UserCategory is PAYER.

IncomeRangeinteger nullable

Returned null if UserCategory is PAYER.

The bracket indicating the income of the individual. The brackets are:

  • 1: < 18K
  • 2: 18K - 30K
  • 3: 30K - 50K
  • 4: 50K - 80K
  • 5: 80K - 120K
  • 6: > 120K
ProofOfIdentitystring nullable

The Id of the KYC Document whose Type is IDENTITY_PROOF if validated for the user. If no identity proof is validated, then this value is null.

ProofOfAddressstring nullable

The Id of the KYC Document whose Type is ADDRESS_PROOF if validated for the user. If no address proof is validated, then this value is null.

Capacitystring

This is a deprecated parameter.

PhoneNumberstring nullable

Format: International E.164 standard (preceded by plus sign and country code) or local format

The individual's phone number. The local format (recommended) requires PhoneNumberCountry to ensure correct formatting.

If present, the phone number forms part of card transaction data that is passed to issuers to improve authentication rates.

For users with UserCategory OWNER , the phone number is used to pre-populate the SCA session for them to confirm and receive an SMS OTP. If the individual modifies the phone number during the session, this data is not updated in the API.

PhoneNumberCountrystring nullable

Format: Two-letter country code (ISO 3166-1 alpha-2 format)

Required if the PhoneNumber is provided in local format (recommended), to render the value in the E.164 standard.

Idstring

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

The unique identifier of the object.

Tagstring

Max. length: 255 characters

Custom data that you can add to this object.

CreationDateinteger

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

PersonTypestring

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.

Emailstring

Format: A valid email address

The individual's email address.

KYCLevelstring

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 whose UserCategory is OWNER can submit verification documents for validation. Only users whose KYCLevel is REGULAR can request payouts.
TermsAndConditionsAcceptedboolean

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.

TermsAndConditionsAcceptedDateinteger nullable

The date and time at which the TermsAndConditionsAccepted value was set to true.

Returned null if UserCategory is PAYER.

UserCategorystring

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 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.
UserStatusstring

Returned values: PENDING_USER_ACTION, ACTIVE, CLOSED

The 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.