Skip to content
A AmunPay API PixVersion 3.38 · updated on Pages

Limits

The limits per transaction, per payer CPF and per payout payee that apply to your account. The lookup always shows the limit in effect today. Check it before promising a high amount to your customer.

GET /v2/ex/limites

Scope: ex.limites.read.

GET /v2/ex/limites
→ 200
{
  "maxDeposito": "15000.00",
  "maxSaque": "15000.00",
  "diarioDepositoCpf": "50000.00",
  "diarioSaqueCpf": "50000.00",
  "mensalDepositoCpf": "500000.00",
  "mensalSaqueCpf": "500000.00",
  "impostoPelaIP": ["maxDeposito", "maxSaque", "diarioDepositoCpf", "diarioSaqueCpf", "mensalDepositoCpf", "mensalSaqueCpf"]
}
Field Type Description
maxDeposito string Limit per charge.
maxSaque string Limit per payout.
diarioDepositoCpf, diarioSaqueCpf string Limit per accounting day: on deposits, per payer CPF; on payouts, per payee, CPF or CNPJ.
mensalDepositoCpf, mensalSaqueCpf string Limit per calendar month, with the same rule as the daily one.
impostoPelaIP list The fields whose limit is the one set by the institution. You cannot raise those through the API.
pedidoPendente object Only appears when there is an increase waiting for the 24 hours. It carries campos, valores and efetivaEm.

A limit with the value 0.00 means no limit.

Change #

PUT /v2/ex/limites

Scope: ex.limites.write.

The body is partial: an omitted field stays as it is. Lowering takes effect immediately. Raising becomes a request that takes effect in 24 hours and appears in pedidoPendente. Setting a field to "0.00" or "" removes your own limit. That counts as an increase: after the 24 hours the limit of the institution applies, and the field appears in impostoPelaIP.

PUT /v2/ex/limites
{
  "maxSaque": "1000.00"
}
→ 200
{
  "maxDeposito": "15000.00",
  "maxSaque": "1000.00",
  "diarioDepositoCpf": "50000.00",
  "diarioSaqueCpf": "50000.00",
  "mensalDepositoCpf": "500000.00",
  "mensalSaqueCpf": "500000.00",
  "impostoPelaIP": ["maxDeposito", "diarioDepositoCpf", "diarioSaqueCpf", "mensalDepositoCpf", "mensalSaqueCpf"]
}

On a payout above a limit, the response is 422 limite_excedido, with tipoLimite, limite and disponivel in violacoes. On a charge the limit applies when the Pix arrives: the charge is created, and a payment above the limit is rejected with the event cob.pagamento_rejeitado (reason LIMITE_EXCEDIDO). On some accounts it also goes back to the payer, with devolucao.criada.

The maximum per payout Pix of some accounts is not one of these limits: it comes from the account, does not change here, and above it the payout responds 422 valor_acima_do_maximo (see Create payout).

Errors #

Status title When
400 valor_invalido Value outside the format "0.00".
400 campo_desconhecido The body is not valid JSON, or it carried a field that is not one of the six limits, or a value that is not text, such as 1000 instead of "1000.00".