> ## Documentation Index > Fetch the complete documentation index at: https://docs.wepayout.co/llms.txt > Use this file to discover all available pages before exploring further. # Rejection Reasons > Understanding payout rejection codes and error messages # Rejection reasons payout One of the key features of our API is the ability to initiate payouts. However, there are multiple reasons for rejection that you should be aware of. These are indicated through the API response. In order for the Payer user to be allowed to issue the payments, rejection reasons are not necessarily immediate but rather a rejection instance. To see all the errors that it is possible to receive: ## Rejection Codes Table | # | Code | Description | | -- | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- | | 1 | Rejected by KYC | The user already has a rejected payer account or is necessary to fill in the banking account that will be used to make the payment | | 2 | Blocked by user | The user has been blocked by the user | | 3 | Blocked contact | The user contact is blocked or invalid or under pattern | | 4 | Max value exceeded per transaction | A transaction with a value that exceeds the maximum value per transaction (for the user's KYC level) | | 5 | Wrong document or not match | The user's document does not match | | 6 | Unauthorized access | The user does not have permission to access the account | | 7 | Unauthorized access | The user does not have permission to access the account | | 8 | Insufficient balance | The user does not have sufficient balance to make the payment | | 9 | Unauthorized access | The user does not have permission to access the account | | 10 | Unauthorized access | The user does not have permission to access the account | | 11 | Payment against bank policy (BIN) | There is a high suspicion that payment will not be processed by the bank due to BIN policy or will be rejected | | 12 | User's wallet is not active | The user's wallet is not active | | 13 | User's wallet is not active | The user's wallet is not active | | 14 | User's wallet is not active | The user's wallet is not active | | 15 | The user does not have a registered wallet | The user does not have a registered wallet | | 16 | The user does not have a registered wallet | The user does not have a registered wallet | | 17 | The user does not have a registered wallet | The user does not have a registered wallet | | 18 | The user does not have a registered wallet | The user does not have a registered wallet | | 19 | The user does not have a registered wallet | The user does not have a registered wallet | | 20 | The user does not have a registered wallet | The user does not have a registered wallet | | 21 | The user does not have a registered wallet | The user does not have a registered wallet | | 22 | The user does not have a registered wallet | The user does not have a registered wallet | | 23 | The user does not have a registered wallet | The user does not have a registered wallet | | 24 | The user does not have a registered wallet | The user does not have a registered wallet | | 25 | The user does not have a registered wallet | The user does not have a registered wallet | | 26 | The user does not have a registered wallet | The user does not have a registered wallet | | 27 | The user does not have a registered wallet | The user does not have a registered wallet | | 28 | The user does not have a registered wallet | The user does not have a registered wallet | | 29 | The user does not have a registered wallet | The user does not have a registered wallet | | 30 | The user does not have a registered wallet | The user does not have a registered wallet | | 31 | PIX not working (processing time) | Error on bank / Contact the bank that makes the PIX payments | **Tip**: To check the list of rejection reasons for payin, please see the [Rejection reasons payin](/payin/rejection-reasons) page. ## Compliance Compliance is crucial and we strictly speaking, reject **OFAC** / **PEP** (Politically Exposed and Sanctioned), **WEpayments** entities. For further information on OFAC and WEpayments compliance standards, please refer to the [Compliance documentation](/compliance). The compliance checks are done in every transaction. If a payer user is flagged as OFAC or PEP, the transaction will be rejected, as well as if the recipient is flagged as OFAC or PEP. ## WEOF are these restrictive lists? The lists are from: * **PEP list** (Politically Exposed Persons) * **OFAC list** (Office of Foreign Assets Control) * **INTERPOL list** * **ONU list** (United Nations Security Council) The lists are updated from time to time by the authorities and the compliance check is done in real time. For more information, please refer to the [Compliance documentation](/compliance). ## Reasons and Descriptions ### Canceled by Compliance - The same as INTERNAL list If this case, the beneficiary's document appears on a CPF or CNPJ with a call of "not issued (called)". Depending on the call, different types of restrictions may apply to the document. For example, if it is a CPF, the restrictions may be related to the person's financial situation or legal status. ### Canceled by Compliance - The same as INTERPOL list If this case, the beneficiary's document appears on the INTERPOL list (list of the INTERPOL). This means that the person is wanted by INTERPOL for some reason. ### Canceled by Compliance - The same as ONU list If this case, the beneficiary's document appears on the ONU list (United Nations Security Council). This list includes individuals and entities that are subject to sanctions by the UN Security Council. The sanctions can be for various reasons, including terrorism, proliferation of weapons of mass destruction, and human rights violations. ### Canceled by Compliance - The same as SANCTION list If this case, the beneficiary's document appears on a Sanctions list. This list includes individuals and entities that are subject to sanctions by various countries and international organizations. The sanctions can be for various reasons, including terrorism, money laundering, and human rights violations. ### Canceled by Compliance - The same as PEP (Politically Exposed Person) list If this case, the beneficiary's document appears on the PEP list (Politically Exposed Person). This list includes individuals who hold or have held prominent public positions, such as heads of state, government officials, and senior executives of state-owned enterprises. PEPs are considered to be at higher risk of being involved in corruption and money laundering. ### Canceled by Compliance - The same as OFAC (Office of Foreign Assets Control) list If this case, the beneficiary's document appears on the OFAC list (Office of Foreign Assets Control). This list includes individuals and entities that are subject to economic sanctions by the United States government. The sanctions can be for various reasons, including terrorism, drug trafficking, and human rights violations. ### Canceled by Compliance - The same as NOT FOUND (no CPF/CNPJ) In this case, the beneficiary's document is not found in the Federal Revenue database. This could mean that the document is invalid or that the person has not registered with the Federal Revenue. In either case, the transaction will be rejected. ## Error Response Example ```json theme={null} { "status": false, "message": "Payment rejected", "data": { "code": "insufficient_balance", "description": "The user does not have sufficient balance to make the payment" } } ``` ## Handling Rejection Errors Check the `code` field in the response to identify the specific rejection reason. Read the `description` field to understand the reason for rejection. Based on the error code, take appropriate action: * Check wallet balance * Verify recipient information * Review compliance requirements * Contact support if needed After correcting the issue, retry the payment request. ## Common Scenarios **Code**: `insufficient_balance` **Solution**: Check wallet balance before creating payment. Use [Get Balance](/api-reference/account/get-balance) endpoint. **Code**: `wrong_document_or_not_match` **Solution**: Verify recipient document number is correct and matches the account holder. **Code**: `blocked_by_compliance` **Solution**: Recipient appears on restrictive lists (OFAC, PEP, etc.). Cannot proceed with payment. **Code**: `max_value_exceeded_per_transaction` **Solution**: Payment amount exceeds the maximum allowed for the user's KYC level. Split into smaller payments or upgrade KYC. ## Best Practices **Check Balance First**: Always verify wallet balance before attempting to create a payment to avoid rejection. **Validate Recipient Data**: Ensure recipient information is accurate and complete before processing payments. **Handle Compliance Rejections**: Implement proper error handling for compliance-related rejections. These cannot be retried and require manual review. ## Related Resources Learn how to create payments with proper validation Understand the Payout solution and payment types Check wallet balance before payments Receive payment status updates