Blocked users
Introduction
As part of MANGOPAY's aim to guarantee the integrity of transactions conducted using its services, and, in accordance with relevant regulations, our teams may block users. Blocking involves the restriction of payment services to a specific end user for reasons of suspected fraudulent behaviour or compliance risk. This page explains the scope of MANGOPAY's blocks on users and the steps that can be taken to unblock them.
Scope of activities that may be blocked
One or both of the following blocks may be applied to a user:
Blocked inflows
A user is unable to make pay-ins or receive transfers from other wallets.
Blocked outflows
A user is unable to make payouts or transfers to other wallets.
Obtaining information about a blocked user
Endpoint
To find out the scope and status of blocks on a specific user, you can use the following call to the Regulatory endpoint:
GET ClientID
/users/userID
/Regulatory
Here is an example response:
{
"ActionCode": "008702",
"ScopeBlocked": {
"Inflows": false,
"Outflows": true
},
"Id": "6639696"
}
Parameters:
ScopeBlocked
: the block status of each scope (inflows and outflows)ActionCode
: a code corresponding to the reasons for the block and actions that can be taken to unblock the userId
: the user ID
Hooks
The following hooks can be set up to receive notifications about blocked users:
USER_INFLOWS_BLOCKED
USER_INFLOWS_UNBLOCKED
USER_OUTFLOWS_BLOCKED
USER_OUTFLOWS_UNBLOCKED
These hooks can be created using:
{
"EventType": "USER_OUTFLOWS_BLOCKED",
"Url": "https://www.test.com",
}
The response will show:
{
"Url": "https://www.test.com"
"Status": "ENABLED"
"Validity": "VALID",
"EventType": "USER_OUTFLOWS_BLOCKED",
"Id": "6639696"
"CreationDate": "1606315995",
}
Once set up, hooks will show:
{
"RessouceId": "6639696"
"EventType": "USER_OUTFLOWS_BLOCKED"
"Date": "1606382707"
}
For more information, please refer to the Hooks section of this documentation.
Taking action to unblock a user
An ActionCode
is included in the response from the endpoint. The following table provides more information on:
- what each code means
- what actions can be taken to unblock the user
- the email address to use for correspondence
ActionCode | Description | Action required | Contact email |
---|---|---|---|
008701 | The user has been blocked because of suspected fraudulent behaviour. | Please contact the MANGOPAY Fraud team. | fraud@mangopay.com |
008702 | The user has been blocked because of a compliance issue. | Please contact the MANGOPAY Compliance team. | legal@mangopay.com |
008703 | The user has been blocked by one of our teams due to a more general issue. | Please contact the MANGOPAY Support team. | support@mangopay.com |
008704 | The user asked for their data to be deleted. Part of that process is to block the user. | Please contact the MANGOPAY Data Protection team. | dpo.mangopay@mangopay.com |
008710 | The user has been identified as potential politically exposed person (PEP). | The user needs to complete the MANGOPAY Declaration Regarding Politically Exposed Persons (English / French). Once this has been completed, please contact the MANGOPAY Compliance team. | legal@mangopay.com |
008711 | The user needs to upload a new proof of ID and a proof of address (e.g. utility bill) to be unblocked. | Please upload a proof of ID and a proof of address (e.g. utility bill) through the dashboard. Once done, contact the MANGOPAY Compliance team. | legal@mangopay.com |
008712 | The user needs to modify his legal personality type and send the proper KYC documents. | Please modify the legal personality type and send the corresponding KYC documents. Once done, please contact the Support team. | support@mangopay.com |
008713 | The user uses a blacklisted IBAN. | Please contact the Fraud team. | fraud@mangopay.com |
008714 | A recent proof of address is required. | Please upload a recent proof of address through the dashboard. | legal@mangopay.com |