API - Feb 26, 2025
API - Feb 26, 2025
User endpoints to enable SCA enrollment
Mangopay is applying strong customer authentication (SCA) on the creation of Natural and Legal users with the UserCategory value OWNER.
SCA requires the Owner user to authenticate with Mangopay directly as they are the Mangopay account holder.
For Natural users, enrollment of the OTP factor is available to integrate, requiring the individual’s PhoneNumber and Email.
For Legal users, enrollment of the OTP factor is available to integrate for Soletraders. The individual’s phone number and email must be provided in LegalRepresentative.PhoneNumber and LegalRepresentative.Email and they must authenticate.
Mangopay started communicating by email about SCA on Owners during February 2025. Your platform will be required to complete the necessary integrations, with specific deadlines communicated during the year.
For any questions, please contact our teams via the Dashboard.
SCA is applicable to Owners in the following scenarios:
- Register an Owner for the first time
- Transition an existing Payer to Owner
- Enroll an existing Owner
- Re-enroll a User (if contact details change)
In each case, your platform must redirect the individual to a Mangopay-hosted webpage. The redirection URL for the SCA session is returned by the Mangopay API in the response property PendingUserAction.RedirectUrl. Before redirecting, you need to define, encode, and apprend a returnUrl to which the session returns the user afterwards (whatever the outcome).
For guidance, see the new Owner SCA section:
Endpoints
There are new SCA-enabled endpoints for the creation and modification of users, as well as a dedicated one to change the UserCategory. The data schema has also changed, see the details for Natural and Legal users.
There is a new endpoint for retrieving an enrollment link for legacy users (and new ones):
There is a new GET endpoint for the new Legal User data schema:
Webhooks
There are new webhook event types to be notified of Owner account SCA enrollment. They are triggered for existing and newly created users but only if UserCategory is OWNER: