Integrators who have chosen the Pix Hub integration path should be aware that this report API only returns transactions processed through PSP Fiserv. Transactions completed through any other PSP routed via Pix Hub will not appear in the report results.
GET /v2/apm/pix/report/transactions
Advanced PIX transaction query, allowing filtering by period, document, Pix key, txid, endToEnd, amounts, transaction types, merchant CNPJ, as well as pagination and multiple integrators. Returns a detailed list of transactions, the criteria used, pagination details, a summary of credits, debits, available balance, and additional messages.
Request Fields
Name
Located in
Description
Mandatory
Type
apikey
header
API Key
yes
string
x-timestamp
header
Date/time of the request (used to prevent replay attacks)
yes
string
x-request-id
header
Random ID used to identify the request
yes
string
x-hmac-signature
header
HMAC signature generated by combining the request parameters: Example: HMAC-SHA256( apikey + x-timestamp + requestBody + URL)
PIX settlement query, allowing filtering by document, period, Pix key, authorization status, and pagination. Returns a detailed list of completed settlements, the criteria used, and pagination information.
Request Fields
Name
Located in
Description
Mandatory
Type
apikey
header
API Key
yes
string
x-timestamp
header
Date/time of the request (used to prevent replay attacks)
yes
string
x-request-id
header
Random ID used to identify the request
yes
string
x-hmac-signature
header
HMAC signature generated by combining the request parameters: Example: HMAC-SHA256( apikey + x-timestamp + requestBody + URL)
Reference table for transaction types used in report endpoints:
Code
Name
Description
0
Payment
Charge
1
Reverse
Reversal
2
Block
MED block
3
Unlock
MED unlock
4
SpecialReturn
Special Return Movement
5
Refund
Partial Refund
6
BacenJudTransfer
Bacen Jud Transfer
7
BacenJudBlock
Bacen Jud Block
8
BacenJudUnlock
Bacen Jud Unlock
9
ScheduledCashOut
Scheduled Cash Out
10
ImmediateCashOut
Immediate Cash Out
11
PixFee
Pix Fee
12
PixFeeReverse
Fee Reversal
13
SpecialReturnReverse
Special Return Reversal
14
ManagementAdjustment
Management Adjustments
15
CashInRejected
Cash-in rejected
16
CashOutRejected
Cash-out rejected
17
DueDatePayment
Due date payment
18
CashOutReverse
Cash Out Reversal
Amount Fields
Rules for the amount and paidAmount fields returned by the transaction report endpoints. In summary endpoints, the values are the sum of the transactions of each type.
Field
Transaction types
Returned value
amount
0 - Payment, 17 - DueDatePayment
Original charge amount
amount
Other types
Transaction amount
paidAmount
0 - Payment, 17 - DueDatePayment
Amount actually paid by the payer. In due date charges, it may differ from amount due to interest, penalty, discount or deduction
paidAmount
1 - Reverse, 13 - SpecialReturnReverse
Split endpoints: amount paid of the original charge. /v2/apm/pix/report/transactions: 0
paidAmount
Other types
0
Settlement Error Codes
Error codes that are returned in the errorMessage field when a settlement fails.
Code
Name
Description
1
InvalidAccount
These are registration errors that require updates to the client's data. Examples: the root CNPJ of the domicile account does not match the CNPJ of the account at the PSP, or the account lacks settlement data.
2
ProcessingFailure
These are internal errors that can be retried. Typical causes include exceptions, timeouts, infrastructure failures, or HTTP call errors. This is the default error for such cases.
3
WithoutBalance
This can occur if, at the time of settlement execution, the sum of returns, refunds, and blocks consumes the total value of received charges, resulting in a zero balance to be settled. The record is created, but it is already assigned this error.
4
BlockedBalanceMED
The available balance is blocked due to fraud prevention triggers or suspicious activity detection. Settlement cannot proceed until the block is manually reviewed and released by the compliance team.
5
BlockedBalance
The available balance is blocked due to pending obligations, judicial holds, or internal compliance restrictions. It requires administrative action or resolution of the underlying issues before settlement can occur
Settlement Status
Code
Name
Description
0
Pending
Settlement awaiting processing — when the account settlement status is Pending.
1
Confirmed
Settlement completed successfully — when the account settlement status is Closed and has no errors.
2
Failed
Settlement failed — when the account settlement status is Failed, or when it is Closed but has an associated error.
Origin Channel
Reference table for origin channels used in report endpoints:
Code
Name
Description
1
ExternalIntegrator
External Integrator
2
ServicesModule
Services Module
3
ClientPortal
Client Portal
4
InternalAutomation
Internal Automation
5
MED
Special Return Mechanism (Mecanismo Especial Devolução)