> For the complete documentation index, see [llms.txt](https://apidocs.onekeypayments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.onekeypayments.com/api-reference/deposits-api/manage-refunds/api-codes.md). # API Codes ## Refunds Status Codes

Status	Description
	The refund is created and is pending to be processed. It can still be cancelled.
	The refund is pending for you to provide more information. It can still be cancelled.
	The refund has been sent to the bank for processing. It can't be cancelled anymore.
	The refund has been manually cancelled. Final status.
	The refund has been rejected by the bank. Final status.
	The refund has been completed. Final status.

{% hint style="success" %} Use the [Refund status endpoint](/api-reference/deposits-api/manage-refunds/get-refund-status.md) to retrieve the status of a refund. {% endhint %} *** ### Refund API Error Codes

API Code	HTTP Code	Type	Message	Description
800	400	`REFUND_NOT_ENABLED`	Refund is not enabled	Your Merchant account doesn't have the refund capability enabled. Check with your Account Manager
801	400	`DEPOSIT_NOT_COMPLETED`	Refund cannot be applied since deposit is not in status completed	The refunds can only be applied over COMPLETED deposits
802	400	`INVALID_AMOUNT_TO_REFUND`	Amount to refund not valid	The amount to refund is not valid. Check if the amount is negative or bigger than the deposit itself.
803	400	`INSUFFICIENT_FUNDS`	Insufficient funds	Your Merchant account doesn't have enough funds to cover for the refund amount
804	400	`MISSING_BANK_ACCOUNT`	Missing bank account information	The bank account information is missing
805	400	`ERROR_IN_REFUND`	Error, the refund was not processed. {details}	The refund could not be completed. Flag it for review on our Merchant Panel for further information

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://apidocs.onekeypayments.com/api-reference/deposits-api/manage-refunds/api-codes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.