---
title: "Submit a Subject Erasure Request."
method: POST
path: "/requestSubjectErasure"
tags: ["General"]
---

# Submit a Subject Erasure Request.

`POST /requestSubjectErasure`

Sends the PSP reference containing the shopper data that should be deleted.

## Request body

- SubjectErasureByPspReferenceRequest
  - `forceErasure` boolean — Set this to **true** if you want to delete shopper-related data, even if the shopper has an existing recurring transaction. This only deletes the shopper-related data for the specific payment, but does not cancel the existing recurring transaction.
  - `merchantAccount` string — Your merchant account
  - `pspReference` string — The PSP reference of the payment. We will delete all shopper-related data for this payment.

## Response `200`

OK - the request has succeeded.

- SubjectErasureResponse
  - `result` 'ACTIVE_RECURRING_TOKEN_EXISTS' | 'ALREADY_PROCESSED' | 'PAYMENT_NOT_FOUND' | 'SUCCESS' — The result of this operation.

## Other responses

- `400` — Bad Request - a problem reading or understanding the request.
- `401` — Unauthorized - authentication required.
- `403` — Forbidden - insufficient permissions to process the request.
- `422` — Unprocessable Entity - a request validation error.
- `500` — Internal Server Error - the server could not process the request.

---

[API](https://skmtc.dev/adyen/apis/adyen-data-protection-api.md) · [All operations](https://skmtc.dev/adyen/apis/adyen-data-protection-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/adyen/adyen-data-protection-api/revisions/de45336da8c3/schema)