> For the complete documentation index, see [llms.txt](https://developer.flash-payments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.flash-payments.com/moving-funds/payouts/rejection-codes.md). # Rejection codes How to handle a payout rejection If your withdrawal is canceled (aka rejected) by our AML and Compliance team, you'll receive the [withdrawal\_cancelled](https://developer.flash-payments.com/webhooks#withdrawal_cancelled) webhook containing both a rejection code (`rejectCode`) and a manually written rejection reason (`statusMessage`). You can find the same two properties within the [`withdrawal`](/moving-funds/payouts/query-withdrawals.md) GraphQL type. Here is a current list of all possible `rejectCode`s, but please note this list **can be extended with time**. ``` CANCELLATION_REQUESTED_BY_PARTICIPANT CANCELLATION_BY_RECIPIENT_FI COMPLIANCE_DECLINED COMPLIANCE_DECLINED_EXTERNAL SENDER_INADEQUATE_DATA SENDER_INVALID_ADDRESS SENDER_INCOMPLETE_ADDRESS RECIPIENT_INADEQUATE_DATA RECIPIENT_INVALID_ADDRESS RECIPIENT_INCOMPLETE_ADDRESS DATA_ENQUIRY_TIME_ELAPSED DATA_ENQUIRY_RESPONSE_INADEQUATE SOURCE_OF_FUNDS_INADEQUATE DUPLICATE_TRANSACTION TECHNICAL_ISSUE RECIPIENT_ACCOUNT_CLOSED RECIPIENT_INVALID_ACCOUNT_NUMBER RECIPIENT_INVALID_BANK_CODE RECIPIENT_INVALID_ACCOUNT RECIPIENT_COUNTRY_NOT_SUPPORTED RECIPIENT_CURRENCY_NOT_SUPPORTED EXPIRED ``` {% hint style="danger" %} **Please note**: `CANCELLED` is a **final** status for **any** withdrawal. \ Please do not retry a withdrawal if it was rejected by our Compliance team or by a beneficiary financial institution. Only those withdrawals rejected with code `TECHNICAL_ISSUE` may be re-submitted as new transactions. {% endhint %} Please also note that while the rejection codes are set, the corresponding free text `statusMessage` will have a case-by-case human written text explaining the root cause of the cancellation. We'll try to be as descriprive as possible taking into account the legal bounds (we are not allowed by the law to disclose certain 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.flash-payments.com/moving-funds/payouts/rejection-codes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.