UserCategory
is PAYER
. The Payer category of user only requires basic information (e.g. name, email address). The Payer category is designed to register individuals or businesses making pay-ins on your platform using a Mangopay payment method.UserCategory
is OWNER
. The Owner category of user requires more detailed information (e.g. date of birth, country of residence), and requires the user to accept Mangopay terms and conditions. The Owner category is designed to register and identify individuals and businesses that are receiving funds from other users, and who can request KYC verification and, once verified successfully, payouts to an external bank account.UserCategory
, PLATFORM
, which represents the platform integrating Mangopay in their app or website. Depending on the platform’s implementation, this value may be assigned to a single user by Mangopay as part of the approved and validated workflow.
The PLATFORM
value:
ClientId
), but more than one is possibleUserCategory
of OWNER
and be KYC verified (KYCLevel
is REGULAR
)PLATFORM
category of user is not affected by the rules being applied to the PAYER
category.
If your platform has a user that should be categorized as the PLATFORM
but isn’t, then please contact Support via the Dashboard.
In addition to the PLATFORM
user, there are other approved and validated users in place for technical in certain approved workflows. These technical users should not be affected by the restrictions being introduced for PAYER
users, either because they do not breach them or because they are categorized as OWNER
. If your platform has any queries about technical users, please contact Support via the Dashboard.
OWNER
. SCA is being introduced on the act of categorizing a PAYER
as an OWNER
, as described in SCA on Users. However, it is still possible to categorize users as OWNER
via the legacy endpoint and via the Dashboard. In this case, the OWNER
must later be enrolled in SCA separately.
In other cases, a more significant change in your integration may be required to align your usage with the restrictions below. We invite you to familiarize yourself with the features impacted by the rules below, consulting the rest of our documentation for the current integration standards. Please contact Support via the Dashboard if you require confirmation on any matter or have a query.
UserCategory
parameter is required on all API calls to create (POST) or update (PUT) a user. While Mangopay policy already requires categorization, the change is being enforced technically.
API calls to the POST or PUT endpoints that don’t contain UserCategory
will return an error.
Example of error that will be returned
UserCategory
of PAYER
are not allowed to receive transfers from other PAYER
or OWNER
users. However, PAYER
users are permitted to transfer funds between wallets belonging to them. PAYER
users can also receive full and partial transfer refunds (as well as full and partial pay-in refunds).
Requests to POST Create a Transfer endpoint where the owner of the CreditedWalletId
is a PAYER
(and not also the owner of the DebitedWalletId
) will fail with the ResultCode
002701.
PaymentRef
parameter is provided on the POST Create a Payout endpoint, with the ReasonType
set to PAYIN_REFUND
and the Id
of the initial pay-in as the ReferenceId
. For more information, see Refunds using payouts.
Otherwise a request to POST Create a Payout endpoint will result in a failed payout with the ResultCode
002701.
Status
being set to REFUSED
and a KYC_FAILED
event.
Example of error that will be returned