# Delete Account
source: https://developer.mastercard.com/payment-account-management/documentation/use-cases/delete-account/index.md

**Scenario** : Issuer has decided to stop providing account updates to participating merchants on behalf of the cardholder. Mastercard designates these requests as 'Override for Deletion'.  

**Description** : In this use case, `/overrideForDeleteAccount` API is used to delete an account from ABU. This will delete an account from ABU and also stop any further account updates to merchants. However, it will not result in associated MDES tokens being deleted. To confirm successful response, the `/requestStatus` API is then sent.

### Consuming Systems {#consuming-systems}

* Account Billing Updater

### APIs used {#apis-used}


API Reference: `GET /overrideForDeleteAccount`


API Reference: `GET /account-maintenance/requestStatus`

### Sequence {#sequence}

Diagram overridefordelete

1. Issuer sends an `/overrideForDeleteAccount` request to PAM API.
2. PAM API will validate the Client ID and PAN checks and send the request to ABU.
3. ABU will remove the account and publish this update to PAM API.
4. Issuer then sends a `/requestStatus` request to confirm if the account updates were successfully consumed by ABU.
5. PAM API will then confirm this update to the issuer with a `/requestStatus` response with a success or the specific error code received from ABU.

Refer to the integration tutorial for details on how to use these endpoints for deleting an account from ABU.

See also: [Error Codes](https://developer.mastercard.com/payment-account-management/documentation/code-and-formats/error-codes/index.md)