OWNER
is created (or categorized as such). In the user endpoints, there is no functionality similar to the ScaContext
and USER_NOT_PRESENT
value being added to transfers and wallet access, because there are no exemptions for account creation.
However, in certain cases we may grant an exemption to this situation if your workflow was built using automated user object creation. In such cases, it is essential that your app or website offers an option for your users to complete their SCA enrollment using the dedicated POST Enroll a User endpoint at the appropriate time.
OWNER
users at certain moments of their activity with Mangopay. Your platform must change its implementation as a result (see integration required for SCA).
Prior to being able to authenticate actions, the user must:
OWNER
UserCategory
)Email
, PhoneNumber
)OWNER
users that require SCA to be performed are:
OWNER
users for use with payouts)OWNER
users)OWNER
users to view wallet balance or list transactionsUSER_NOT_PRESENT
value of the new parameter ScaContext
. These requests will not initially require SCA redirection.
Over time, Mangopay will analyze the adoption of SCA and may be required to take appropriate action to ensure compliance. Mangopay’s objective is to protect your users when they benefit from our services, via an authentication solution that is easy for your platform to adopt in its existing integration.
For more details, see the transfers guide.
USER_NOT_PRESENT
value for ScaContext
allows platforms to identify actions where SCA redirection will not be immediately required.
The use of this feature for actions taken on behalf of users, without their direct involvement, may be possible if the platform can demonstrate that it has the legal capacity to perform an action falling within the scope of the SCA on behalf of a third party. This legal capacity may result, for example, from a contractual arrangement (such as a mandate or representation contract) or another specific legal provision that would authorize the platform to act in this way.
We remain committed to maintaining the highest standards of security and compliance, and Mangopay will analyze such cases over time to determine the appropriate SCA arrangement.
BankAccountId
) for payouts.
ACTIVE
as their UserStatus
, will not be restricted or transitioned to PENDING_USER_ACTION
if you attempt to enroll them using POST Enroll a User and the SCA session is not successful.
On Recipients, Transfers, and Account Access they will also not be restricted (their status remains ACTIVE
), but the relevant action will not succeed. In this case, you need to retry the Recipient creation or Transfer to allow the user to complete SCA successfully.
Mangopay may be required to start introducing consequences on users if they haven’t enrolled in SCA, but this will be done with sufficient notice to platforms. You will also be informed of the consequences of non-enrollment, which may include removing certain permissions, blocking the account, reverting the category to PAYER
, or closing the account.
Mangopay’s objective is to protect your users when they benefit from our services, via an authentication solution that is easy for your platform to adopt in its integration. We remain committed to maintaining the highest standards of security and compliance.
See the guide section on existing user integration →