Rejection reasons payout

A payout can be refused at two different moments:

When the request is sent: the API answers with an HTTP error and the payout is not created. See Request refused.
After the payout is created: the API answers 201 with status Awaiting (7), and the payout is later Canceled (6) or Rejected (4) during processing (compliance checks, balance, limits, beneficiary data, Pix key or bank response). See Payout canceled or rejected after creation.

This page describes the behavior of the Create Payment endpoint (POST /v2/payout/payments).

Request refused

When the request is refused, no payout is created and you can fix the data and send the request again.

HTTP status	When it happens
`400`	The request could not be processed, for example the same `invoice` was sent again while the previous request is still being processed, or the bank account data is invalid.
`401`	The access token is missing, invalid or expired.
`403` / `404`	The merchant informed in `merchant_id` was not found, is disabled or is not available for your user.
`422`	One or more fields are invalid. See Validation errors.
`451`	The beneficiary account is not one of the accounts authorized for your account (only when this restriction is enabled for your account).
`503`	The service is temporarily unavailable for scheduled maintenance. Retry after the time informed in the `Retry-After` header.
`500`	Unexpected error. Try again later or contact support.

Validation errors

Validation errors return HTTP 422 with the list of invalid fields in errors. Each field can have more than one message.

{
  "message": "The given data was invalid.",
  "errors": {
    "beneficiary.document.number": ["The document provided is not a valid CPF."],
    "pix.pix_key": ["Pix key type not identified. Review the pix_key value."]
  }
}

Besides the standard messages for required fields, formats and sizes, these are the most common validation errors:

Field	Message	What to do
`beneficiary.document.number`	The document provided is not a valid CPF. / CNPJ.	Check the beneficiary CPF or CNPJ.
`pix.pix_key`	Pix key type not identified. Review the pix_key value.	The value does not match any accepted format, for example a phone that is not a Brazilian mobile number with exactly 14 characters or an e-mail longer than 77 characters. See Accepted PIX key formats.
`pix.pix_key`	The pix.pix key is not a valid cpf. / cnpj.	The Pix key looks like a CPF or CNPJ but the number is invalid.
`pix.pix_key`	Token Bucket request limit exceeded.	The Pix key query limit was reached. Wait and try again.
`invoice`	The invoice has already been taken.	Another payout already uses this `invoice` (only when unique invoice is enabled for your account). Use a new `invoice`.
`payment_method`	The payment method informed is not enabled.	The payment method is not enabled for your account. Contact support.
`beneficiary.document.type` / `pix.pix_key`	The transaction is restricted because legal entities are not allowed to place requests in this scenario.	Payouts to a CNPJ are not allowed for your account.
`originator_legal_entity`	The provided originator is invalid, not approved, or not authorized for this merchant.	Check the originator data sent in the request.
`markup`	Markup errors	Check the `markup` object. See Submerchant markup.

Payout canceled or rejected after creation

After a payout is created, it can be Canceled (status 6) during processing. When this happens, the payout webhook includes the status_detail object with the reason:

{
  "id": 123456,
  "invoice": "INV-0001",
  "status": {
    "id": 6,
    "name": "Canceled"
  },
  "updated_at": "2026-09-30 10:15:00",
  "status_detail": {
    "code": "47",
    "detail": "Insufficient Balance"
  }
}

status_detail.code identifies the reason. Use this field in your integration.
status_detail.detail is a human-readable description, in the language configured for your user. The text may change, so do not use it to implement rules.

The same description is returned in the rejection_description field when you get the payout.

TED payouts rejected by the beneficiary bank end with status Rejected (4). In this case, the reason is available in the rejection_description field.

Rejection codes table

Beneficiary and bank data

Code	Reason	What to do
`1`	Rejected by bank	The beneficiary bank rejected the payment. Check the beneficiary data.
`2`	Invalid document or bank data	Check the beneficiary CPF/CNPJ and bank account data.
`3`	Blocked account	The beneficiary account is blocked. Ask the beneficiary for another account.
`4`	Divergent beneficiary	The account or Pix key does not belong to the informed document. Check the beneficiary data.
`5`	Wrong bank account or branch	Check the branch and account number.
`6`	Wrong bank code	Check the bank code or ISPB.
`7`	Wrong bank branch	Check the branch number.
`8`	Wrong bank account	Check the account number and digit.
`9`	Wrong name	Check the beneficiary name.
`10`	Wrong bank details	Check the beneficiary bank data.
`15`	Irregular CPF	The beneficiary CPF is irregular.
`20`	Divergence in CPF/CNPJ information	The informed CPF/CNPJ does not match the account holder.
`22`	Account closed	The beneficiary account is closed. Ask the beneficiary for another account.
`29`	Beneficiary’s bank does not allow payment type indicated	The beneficiary bank does not accept this payment type.
`30`	Account does not allow payment type indicated	The beneficiary account does not accept this payment type (for example, salary accounts).
`31`	Incorrect account type	Check the account type (checking, savings, payment or salary).
`32`	Pix rejected by beneficiary bank	The beneficiary bank rejected the Pix. Check the beneficiary data or ask for another account.

Pix

Code	Reason	What to do
`17`	Invalid pix key	The Pix key does not exist or is invalid. Check the key with the beneficiary.
`26`	Beneficiary’s bank does not allow payment type indicated	The beneficiary bank does not support this Pix operation.
`27`	DICT Quota Exceeded	The Pix key query limit was reached. Send the payout again later.
`46`	Token Bucket request limit exceeded	The Pix key query limit was reached. Send the payout again later.
`48`	Pix key entry blocked	The Pix key is blocked. Ask the beneficiary for another key.
`53`	Failed to send to bank	The payment could not be sent to the bank. Send the payout again.

Compliance and antifraud

Code	Reason
`28`	Canceled by Compliance
`33`	Canceled by Compliance. Tax number on OFAC list
`34`	Canceled by Compliance. Tax number on INTERPOL list
`35`	Canceled by Compliance. Tax number on ONU list
`36`	Canceled by Compliance. Tax number on EUROPEAN list
`37`	Canceled by Compliance. Tax number is disabled (deceased)
`38`	Canceled by Compliance. Tax number is PEP (politically exposed person)
`39`	Canceled by Compliance. Tax number blocked on RFB (Brazilian Federal Revenue Office)
`40`	Canceled by Compliance. Canceled due to CPF restriction underage Brazilian law
`41`	Canceled due to restriction age (over 80 years old) as per compliance policy
`43`	Restricted by KYC
`51`	Payment rejected after preventative review
`52`	Transaction canceled. The recipient’s document is irregular with the Federal Revenue Service or appears on international restrictive lists
`54`	Transaction rejected. The payer’s document is irregular with the Federal Revenue Service or appears on international restrictive lists

See Compliance for more details. Compliance cancellations cannot be retried.

Balance and limits

Code	Reason	What to do
`14`	The payment amount is above the allowed for the account type	Reduce the amount or use another beneficiary account.
`18`	Value exceed the max amount	The amount is above the maximum allowed. Reduce the amount.
`47`	Insufficient Balance	Check your balance with Get Balance before sending the payout again.
`49`	Transactional limit exceeded	The amount is above your transactional limit. Contact support to review your limits.

Account restrictions

Code	Reason	What to do
`WE0001`	The payment was made to an unregistered account	The beneficiary account is not one of the accounts authorized for your account.
`WE0002`	The payment was made to an unauthorized institution	The beneficiary institution is not authorized for your account.

Other reasons

Code	Reason	What to do
`11`	Canceled due to duplicated invoice	Another payout with the same `invoice` already exists.
`13`	Client request payment cancelation	The payout was canceled at your request or by a restriction configured for your account (for example, a blocked beneficiary).
`16`	Cancelation requested by client	The payout was canceled at your request.
`42`	Canceled due to external error	The payment could not be completed by the receiving institution or payment network. Check the beneficiary data and send the payout again, or contact support.

A payout returned by the beneficiary after it was paid is not a rejection: it keeps the Paid status and receives a refund substatus.

To check the list of rejection reasons for payin, please see the Rejection reasons payin page.

Compliance

Every payout goes through compliance checks. The beneficiary document is verified against restrictive lists and compliance policies:

OFAC list (Office of Foreign Assets Control): code 33
INTERPOL list: code 34
UN list (United Nations Security Council): code 35
European Union list: code 36
Deceased persons (document disabled): code 37
PEP list (Politically Exposed Persons): code 38
Brazilian Federal Revenue (document irregular or blocked): code 39
Age restrictions (underage or over 80 years old): codes 40 and 41
KYC restrictions: code 43
Other compliance restrictions: code 28

Payouts can also be canceled after a preventative antifraud review (codes 51, 52 and 54).

When the compliance check needs a manual review, the payout is not canceled: it goes to In Review (5) until the review is finished. See Payout Status Flow.

Handling Rejection Errors

Identify the Error

If the request was refused, check the HTTP status and the errors object. If the payout was canceled after creation, check status_detail.code in the webhook.

Review the Description

Use the tables on this page to understand the reason for the rejection.

Take Corrective Action

Based on the error code, take appropriate action:

Check wallet balance
Verify recipient information
Review compliance requirements
Contact support if needed

Retry the Request

After correcting the issue, send a new payout request. Compliance cancellations cannot be retried.

Common Scenarios

Insufficient Balance

Code: 47Solution: Check wallet balance before creating payment. Use Get Balance endpoint.

Invalid Pix Key

Code: 17Solution: Verify the Pix key with the beneficiary before sending the payout again.

Compliance Block

Codes: 28, 33 to 43Solution: Recipient appears on restrictive lists (OFAC, PEP, etc.) or does not meet compliance policies. Cannot proceed with payment.

Transactional Limit Exceeded

Code: 49Solution: Payment amount exceeds your transactional limit. Split into smaller payments or contact support to review your limits.

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.

Create Payment

Learn how to create payments with proper validation

About Payments

Understand the Payout solution and payment types

Get Balance

Check wallet balance before payments

Callback Payment

Receive payment status updates

Introduction

Account

Banks

Payin

Payout

Markup

Rejection Reasons

Rejection reasons payout

Request refused

Validation errors

Payout canceled or rejected after creation

Rejection codes table

Beneficiary and bank data

Pix

Compliance and antifraud

Balance and limits

Account restrictions

Other reasons

Compliance

Handling Rejection Errors

Common Scenarios

Insufficient Balance

Invalid Pix Key

Compliance Block

Transactional Limit Exceeded

Best Practices

Create Payment

About Payments

Get Balance

Callback Payment

​Rejection reasons payout

​Request refused

​Validation errors

​Payout canceled or rejected after creation

​Rejection codes table

​Beneficiary and bank data

​Pix

​Compliance and antifraud

​Balance and limits

​Account restrictions

​Other reasons

​Compliance

​Handling Rejection Errors

​Common Scenarios

Insufficient Balance

Invalid Pix Key

Compliance Block

Transactional Limit Exceeded

​Best Practices

​Related Resources

Create Payment

About Payments

Get Balance

Callback Payment

Rejection reasons payout

Request refused

Validation errors

Payout canceled or rejected after creation

Rejection codes table

Beneficiary and bank data

Pix

Compliance and antifraud

Balance and limits

Account restrictions

Other reasons

Compliance

Handling Rejection Errors

Common Scenarios

Best Practices

Related Resources