Skip to main content

Request Customer Deactivation

POST 
/v2/customers/:customerId/deactivations

Allows Partner to request customer deactivation. All customer wallets are eligible for deactivation as long as the following criteria are met:

  • customer wallet has exactly zero balance
  • no pending transactions
  • no active restrictions with reason Compliance added by Paysafe - restrictions should be resolved prior to being eligible for deactivation.

One of the mandatory fields for customer deactivations is the deactivation category. Possible values are:

  • CUSTOMER_INITIATED
  • MERCHANT_INITIATED

The reason for customer deactivation is also a mandatory field. Some of the possible values are:

  • FRAUD
  • INACTIVITY
  • T_C_ABUSE
  • NO_SERVICE_COUNTRY
  • OTHER

All possible values can be seen bellow.

Upon requesting a customer deactivation, the customer will be restricted for All Transactions and the deactivation request will be posted for manual review by out team. If the deactivation is approved, the customer will be restricted for Login. Otherwise, the restriction for All Transactions will be lifted. In both cases, the Partner will receive a webhook with the deactivation outcome and additional information if applicable. For more information regarding the webhook, please refer to the official webhook documentation.

The response returns the deactivation request. If there is an existing customer deactivation request in MANUAL_REVIEW status, the API will 409 Conflict.

Request​

Responses​

Created