Create Pix Devolution
POST/v1/pix/devolutions
Initiate a new pix devolution by providing the required information in the request body and executing the request.
Request
Header Parameters
- If there's no value: The default protection checks that the values in this request are equal: { method, params, path, query, body, userId }. This means that if a request repeats the same values, it will be blocked.
- 'nonce': The nonce and { method, params, path, query, body, userId } value are checked. When the protection schema is this, requests will be OK if this nonce value is different in each request.
- 'x-transaction-uuid': The transactionId and { method, params, path, query, body, userId } value are checked. Requests will be OK if this x-transaction-uuid value is different in each request.
- 'x-transaction-uuid&nonce' or 'nonce&x-transaction-uuid': The nonce, transactionId value and { method, params, path, query, body, userId } are checked, i.e. if requests are repeated the same value in both fields, they will be blocked. But if any field has a different value, the request is OK.
The replay-protection-schema allows the user to choose between 3 options:
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
- application/json
Body
required
Charge back the operation ID listed on the credit statement.
Possible values: >= 1
Value in R$ cents. Should be less or equal then credit transacation.
User defined payment description.
User defined payment merchant ID.
Responses
- 201
- 400
- 401
- 422
The devolution returned successfully.
- application/json
- Schema
- Example (from schema)
Schema
Devolution ID.
Value in R$ cents.
User defined devolution description.
Possible values: [PENDING, WAITING, WAITING_DELAYED, CONFIRMED, ERROR, FAILED, CANCELED]
Devolution state.
Devolution created at.
{
"id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"amount": 1299,
"description": "User defined description",
"state": "PENDING",
"created_at": "2026-03-26T14:02:58.527Z"
}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.