Get transaction status by E2E or identifier
Queries a PIX transaction by E2E (End-to-End ID) or identifier at the settlement bank, at the time of the call.
This route is an alias of GET /v1/accounts/{accountId}/statement: the
response is always the statement list payload (items[]), never a
single object.
- With
endToEndIdoridentifierit is an exact lookup:itemsholds 0 or 1 transaction, and pagination, dates andoperationare ignored. When both are sent,identifieris tried first andendToEndIdis used if it finds nothing. - A transaction that does not exist is not a
404: the response is200withitems: []andtotalElements: 0. - Without either parameter the route returns the paginated statement,
with the same parameters and rules as
GET /statement.
Each item has the AccountStatementEntry shape. direction is IN
(received) or OUT (sent), and amount is negative on OUT.
Important: Only completed or attempted PIX transfers appear here. QR Codes that
were never paid are not transactions (they have no E2E ID). To query QR Code status
regardless of payment, use GET /v1/accounts/{accountId}/pix/qr-code/lookup.
To get the payment as a single object (with hold, partnerStatus and
waitForFinalStatus), use GET /v1/accounts/{accountId}/pix/payments/lookup.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Headers
Query parameters
Transaction E2E ID (format E + ISPB + date + sequence). endToEnd
is accepted as an alias.
Charge identifier (txid) or internal reference.
Response
Statement list payload. On an exact lookup, items holds the
transaction found, or is empty when there is none.
Page of statement rows. Length may be less than size.
Zero-based page index.
Requested page size (ceiling). items may be shorter.
Total lines in the settlement-bank statement window. Approximate when rows are omitted after pagination.