API - Feb 19, 2026

Changed

Rules preventing Natural Users being used for non-personal accounts

To protect your platform and users, Mangopay now implements rules to prevent the Natural User object being used for individuals or entities whose activity should be registered and verified accordingly (as a Legal User, for example Soletrader).

To this end, Mangopay analyzes data in the Natural User object:

• The Email property must contain a personal email address – for example, using an individual’s name, such as john.doe@example.com, john@doe.com, or similar. Mangopay implements a rule that analyzes the word or characters before the @ sign and the use of generic or professional words is not allowed – examples include info@example.com and hr@example.com.
• The FirstName and LastName properties must contain personal names. Mangopay analyzes these fields for indicators of legal entities such as Ltd, GmbH, or SAS.

These rules may return an error when creating or updating a User with the UserCategory of OWNER on the following endpoints:

• POST Create a Natural User
• PUT Update a Natural User
• PUT Categorize a Natural User

A user with the PAYER category is not impacted unless or until your platform attempts to assign them the OWNER value.

These rules apply in Production and Sandbox.

When either of these rules is triggered by one of the API calls above, the API returns this error:

1
{
2
    "Message": "The data you provided does not comply with our anti-fraud policy",
3
    "Type": "fraud_policy",
4
    "Id": "51876239-4814-422e-8f4b-6986520414bb#1750420019",
5
    "Date": 1750420020,
6
    "errors": null
7
}

Related to this change, the article on user types has been updated, including with guidance on when to register a user as a Natural User or Legal Soletrader.