---
title: "Initiate account closure request"
method: POST
path: "/v1/account_closure_requests"
tags: ["Account closure requests"]
---

# Initiate account closure request

`POST /v1/account_closure_requests`

Creates an account closure request for the specified account. See the [account closure guide](https://docs.solarisgroup.com/guides/compliance/account-closure/) for more information about this process and the associated stages.

## Request body

- AccountClosureRequestCreateRequest
  - `account_id` string, required — ID of the account to be closed.
  - `closure_reason` 'ACCOUNT_REVOCATION' | 'CUSTOMER_WISH' | 'PARTNER_SERVICE_ACCOUNT_TERMINATED' | 'RELATIONSHIP_TERMINATION' | 'COMPLIANCE_IMMEDIATE_PARTNER', required — List of possible reasons for an account closure request initiated by a partner.

## Response `200`

The operation was successful (idempotency).

- AccountClosureRequest
  - `id` string — ID of the account closure request.
  - `closure_reason` 'ACCOUNT_REVOCATION' | 'ACCOUNT_REVOCATION_INTERNAL' | 'COMPLIANCE_IMMEDIATE_INTERNAL' | 'COMPLIANCE_IMMEDIATE_PARTNER' | 'COMPLIANCE_ORDINARY_INTERNAL' | 'CUSTOMER_WISH' | 'CUSTOMER_WISH_INTERNAL' | 'DUNNING_DECOUPLED_CARD_INTERNAL' | 'FATCA_STATUS_INELIGIBLE_IMMEDIATE' | 'FATCA_STATUS_INELIGIBLE_ORDINARY' | 'INSOLVENCY_IMMEDIATE_INTERNAL' | 'INSOLVENCY_ORDINARY_INTERNAL' | 'KYC_ORDINARY_INTERNAL' | 'PARTNER_SERVICE_ACCOUNT_TERMINATED' | 'RELATIONSHIP_TERMINATION' | 'RELATIONSHIP_TERMINATION_INTERNAL' | 'SEIZURES_ORDINARY_INTERNAL' | 'TAX_ID_CHANGE_ORDINARY' | 'TECHNICAL_IMMEDIATE_INTERNAL' | 'TERMS_AND_CONDITIONS_BREACH_IMMEDIATE' | 'TERMS_AND_CONDITIONS_BREACH_ORDINARY' | 'WRONG_ACCOUNT_TYPE' — List of possible reasons for an account closure request initiated by Solaris.
  - `status` 'INITIATED' | 'CONFIRMED' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED' | 'REVOKED' — Possible status values for an account closure request.
  - `account_id` string — ID of the account to be closed.
  - `technical_closure_date` string, date — The date when the account was removed from the Solaris system.
  - `legal_closure_date` string, date — The date when the contractual relationship underlying the product/account ends.
  - `failure_reason` object — An object containing information about the reason why an account closure request has failed.
    - `code` 'account_inactive' | 'negative_balance' | 'positive_balance' | 'accrued_interest' | 'forced_failure' | 'processing_timeout' — Code value describing the failure_reason.
    - `detail` 'Account already technically closed.' | 'Account balance is negative, can't perform technical closure.' | 'Account balance is positive, can't perform technical closure.' | 'Accrued interest found on the account, can't perform technical closure.' | 'Account Closure was manually stopped. Please contact Solaris Customer Support for details.' | 'Account Closure failed. Please contact Solaris Customer Support for details.' — Additional details about the failure_reason. Check the guide for the [mapping](https://docs.solarisgroup.com/guides/compliance/account-closure/#failure-reasons) between the values of the fields `code` and `detail`.
  - `payout_allowed` false | true — payout_allowed is deciding whether the funds can be paid out in the automated process, but it also serves as information for the Partner on whether or not the Customer is allowed to pay out funds from the account.
  - `updated_at` string, date-time — Updated date and time

## Other responses

- `201` — The account closure request was successfully initiated.
- `400` — An error occurred on the client side.
- `500` — Internal server error.

---

[API](https://skmtc.net/solarisgroup/apis/account-management.md) · [All operations](https://skmtc.net/solarisgroup/apis/account-management/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/solarisgroup/account-management/revisions/099ef636a5a1/schema)