Choose the default behavior when the ban was specific to one user—for example, a false positive on an individual fraud flag, or a localized compliance issue that has been resolved for that account alone.
Unban users and restore account access
When a banned user needs to regain access, you can restore their account through the admin tooling endpoint. This guide explains how unbanning works for users who share a contact with other accounts.
Default unban behavior
When you unban a user, the system restores access in two steps:
The target user is unbanned and reactivated.
The shared contact is marked as unbanned.
This ensures the user can log in and receive payouts again. If the user shares a contact with other banned users, only the target user and the contact itself are restored by default. Other connected users remain banned unless you explicitly include them.
The contact is always unbanned along with the target user, because a banned contact would block payouts even if the user account is cleared.
Unban connected users
Some situations require unbanning all users tied to the same contact—for example, when a fraud review clears the entire group or when the original ban should not have affected linked accounts.
To unban connected users along with the target user, set the unban_connected_users flag to true in your request. This expands the unban to include:
The target user
The shared contact
All other banned users on that contact
Connected users are only unbanned if they are currently in a banned state. Users who are already active are unaffected.
Request format
Send a POST request to the unban endpoint with the following fields:
Field | Type | Required | Description |
|---|---|---|---|
| integer | Yes | The ID of the user to unban. |
| string | Yes | Your name or identifier for the audit log. |
| string | Yes | The reason for unbanning. Cannot be blank. |
| boolean | No | Set to |
Example request (default behavior)
{
"user_id": 12345,
"unbanned_by": "[email protected]",
"reason": "Fraud review cleared the account"
}Example request (including connected users)
{
"user_id": 12345,
"unbanned_by": "[email protected]",
"reason": "Contact-level ban reversed after manual review",
"unban_connected_users": true
}Responses
The endpoint returns a simple success or failure response:
Success:
{"success": true}Failure:
{"success": false}with HTTP 400 if the request is invalid or the user is not currently banned.
If the target user is not banned, the request fails with the error: Cannot unban a user that is not banned.
What happens after unban
When a user is unbanned:
Their account status changes from banned to active.
The unban reason and your identifier are logged to the user's history.
The user is reactivated and can log in immediately.
Any associated contact is cleared so payouts can resume.
Users do not receive an automatic notification when they are unbanned. If the user needs to know their access has been restored, contact them directly.
When to use each approach
Use default unban (no connected users)
Use connected-user unban
Enable unban_connected_users when the original ban affected an entire contact group incorrectly, or when a review clears all users tied to that contact. This prevents linked accounts from remaining in a banned state while the primary user is restored.
Permissions and access
The unban endpoint requires login. Only operators with appropriate access should use this workflow. If you are unsure whether you have permission to unban users, check your role in Advanced → Team Management or contact your workspace admin.
For more information on roles and permissions, see Team Roles and Dashboard Access.
Related content
Why is my account flagged or under review? — User-facing explanation of account restrictions.
When will I hear back about my payout review? — Timing expectations for reviews.
Was this helpful?
Was this helpful?