Introduction

The temporary Pix limit lets the integrator partner declare, for an account it owns, an additional Pix volume to be transacted during the day — useful for planned batch payment days on which the volume to be sent exceeds the account's current Pix limit.

The temporary volume runs on a counter that is independent of the account's standard Pix limit. Transfers made through the temporary Pix transfer endpoint do not consume the standard limit, and the standard limit remains fully available for normal Pix transfers.

Each integration has a daily automatic-approval ceiling, agreed in advance with QI Tech. Requests that fit within that ceiling — counting what the integration already has approved for other accounts in the day — are approved immediately; above it, approval is manual.

info

The feature is enabled on demand. While the temporary Pix limit is not enabled for your integration, the endpoints in this section respond PXT000206.

Flow

The partner requests an temporary Pix limit for an account, informing the total volume it intends to transact in the day (Request an temporary Pix limit).
Within the integration's automatic-approval ceiling, the request is approved immediately and the limit can already be used.
Above the ceiling, the request goes to QI Tech's manual analysis, which may approve or refuse it. While pending it does not release transfers; the outcome arrives by webhook.
Once the request is approved, the partner performs as many transfers as it wants through the temporary Pix transfer endpoint, up to the declared volume (Perform an temporary Pix transfer).
As long as nothing has been transferred, the partner may cancel the request (Cancel a limit request).
At the end of the Pix day, every request still open is expired automatically.

Time windows

The times below are in Brasília time (BRT or UTC/GMT -03:00).

Operation	Window
Request an temporary Pix limit	06:00 to 17:00
Cancel a limit request	06:00 to 17:00
Perform an temporary Pix transfer	06:00 to 20:00

caution

The request window closes at 17:00, three hours before the execution window. A request can neither be created nor cancelled after 17:00, even if there is still volume available to transfer until 20:00. Outside the request and cancellation window the response is PXT000200; after 20:00 the transfer responds PXT000204.

Notes

The most recent request replaces the previous one, it does not add up. When you create a new request for the same account the volumes do not add up: the total_amount of the most recent approved request applies. If you have already transferred R$ 300,000.00 and a request of R$ 500,000.00 becomes the effective one, the remaining volume is R$ 200,000.00, not R$ 500,000.00.
An approved request stays usable while an increase waits for manual analysis. If the new total_amount is an increase that exceeds the integration's automatic-approval ceiling, the new request is created as pending_approval and the approved one remains approved — you keep transferring within it. When QI Tech approves the new one, the previous one becomes cancelled and the new total applies; if QI Tech refuses it, the previous one stays in force. An account has at most one approved request and at most one under analysis at the same time.
Reducing the total is immediate. A new total_amount lower than or equal to the approved one is approved on the spot and replaces it, with no manual analysis.
A new request's total_amount cannot be lower than the volume already transacted during the day through temporary Pix on that account, precisely because the new request replaces the previous one. If it is, the response is PXT000202.
Reducing an already approved request is approved immediately. If the open request is approved and you create a new one for the same account with a total_amount lower than or equal to the approved one, the new request is also born approved, even when the amount is above your automatic-approval ceiling — reducing does not widen your exposure. Raising the amount goes through the normal rule again and may fall to manual analysis, including when the new amount was already approved earlier the same day.
Cancellation is only possible while the account has transacted no temporary Pix volume during the day. After the first transfer the account stays covered by an active request until 20:00, so that transacted volume is never left without a request authorising it — the response is PXT000201.
Reusing a request_control_key is rejected, not replayed. When you repeat a request_control_key already used in an temporary Pix transfer, the request is refused; the original transfer is not returned nor re-executed. Send a new key for each transfer.
Declaring far more than you transact has a cost. See Underutilization — heavily underutilized requests move the requester to permanent manual analysis.
Temporary Pix transfers do not consume the account's standard Pix limit and do not appear in the usage reported by the limit inquiry.
The temporary Pix transfer body accepts only the manual type, with the destination account data. Transfers by Pix key or QR Code are not supported on this endpoint.

Temporary Pix Request Status

Enumerator	Description
approved	Request approved and available for use during the day
pending_approval	Request under QI Tech's manual analysis, which may approve or refuse it. Not yet usable
rejected	Request refused in the manual analysis. Final state
cancelled	Request cancelled by the partner or replaced by a more recent request for the same account. Final state
expired	Request expired at the close of the Pix day. Final state

Underutilization

At the close of the Pix day, each request still approved is graded on its unused volume. If the unused volume is greater than or equal to 10% of total_amount, QI Tech:

sends the baas.pix.exceptional.underutilized webhook; and
moves the requester to mandatory manual analysis for all future temporary Pix limit requests.

This changes how your future requests are handled

The mandatory manual analysis is permanent and is not reverted automatically. From then on, every temporary Pix limit request from the requester — including those that would be within the automatic-approval ceiling — responds 202 with pending_approval and depends on QI Tech's manual approval before it is usable. Declare a total_amount close to the volume you actually intend to transact.

Webhooks

The three events below are sent to the requester. The body is the same object returned by the limit requests inquiry, with the additional fields indicated.

Event	When it is sent
`baas.pix.exceptional.approved`	A request under manual analysis was approved and can already be used
`baas.pix.exceptional.rejected`	A request under manual analysis was refused. Carries `rejected_reason` when informed
`baas.pix.exceptional.underutilized`	An approved request was heavily underutilized at the close of the Pix day

info

Automatic approval — the request that is born approved within the ceiling — does not generate a webhook: the 201 of the creation itself already reports the outcome.

Webhook Body: baas.pix.exceptional.approved

{
  "pix_request_key": "9c3b7d21-8f4a-4c2b-9e1d-7a6b5c4d3e2f",
  "account_key": "0f2a1e4c-1111-2222-3333-444455556666",
  "total_amount": 1200000.00,
  "status": "approved",
  "message": "Request approved and available for use today until 20:00."
}

Webhook Body: baas.pix.exceptional.rejected

{
  "pix_request_key": "9c3b7d21-8f4a-4c2b-9e1d-7a6b5c4d3e2f",
  "account_key": "0f2a1e4c-1111-2222-3333-444455556666",
  "total_amount": 1200000.00,
  "status": "rejected",
  "message": "Request rejected after manual analysis.",
  "rejected_reason": "Volume incompatível com o histórico da conta"
}

Webhook Body: baas.pix.exceptional.underutilized

{
  "pix_request_key": "9c3b7d21-8f4a-4c2b-9e1d-7a6b5c4d3e2f",
  "account_key": "0f2a1e4c-1111-2222-3333-444455556666",
  "total_amount": 1200000.00,
  "status": "expired",
  "message": "Request expired and no longer available for use.",
  "used_amount": 150000.00,
  "unused_amount": 1050000.00,
  "max_unused_amount": 240000.00,
  "requires_manual_approval": true
}

Webhook Body Params

Field	Type	Description
`pix_request_key`	uuidv4	Unique identification key of the temporary Pix limit request.
`account_key`	uuidv4	Account the request applies to.
`total_amount`	number	Total volume declared for the day.
`status`	enumerator	Request status. See Temporary Pix Request Status.
`message`	string	Descriptive text of the status, in English.
`rejected_reason`	string	Reason for the refusal, when informed. Optional — it may not come even on a refused request.
`used_amount`	number	Volume actually transacted. Present only on the underutilization event.
`unused_amount`	number	Volume declared and not transacted. Present only on the underutilization event.
`max_unused_amount`	number	Unused volume from which underutilization is characterized. Only on the underutilization event.
`requires_manual_approval`	boolean	Indicates that the requester's future requests will require manual analysis. Only on underutilization.

Flow​

Time windows​

Notes​

Temporary Pix Request Status​

Underutilization​

Webhooks​

Webhook Body Params​