Get transaction status by E2E or identifier
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).
Charge identifier (txid) or internal reference.
Response
Canonical transaction status:
INITIATED— created, not yet sent to BACENPENDING_APPROVAL— held inside the settlement bank. Ambiguous on purpose (kept for backward compatibility): it covers both the settlement bank’s internal authorisation queue and its risk review, and it never means an approval is pending on your side or on ours. Readholdto know who is holding the order.PROCESSING— sent to BACEN, awaiting settlementCOMPLETED— confirmed by BACENFAILED— rejected/failed (see error fields)REVERSED— returned/refunded after settlement. The refund details (D-code, amount, date) are not in this payload — see the transaction timeline.
Direction:
IN— Receipt (credit)OUT— Send (debit)
Transaction date/time in RFC3339 with São Paulo offset (-03:00).
Client-provided identifier (if any).
Raw status at the settlement bank, echoed in a clearly named field
(never in status). Present only when the settlement bank reports
one. These are the settlement bank’s own values and may change
without notice — do not use them in status comparisons; they exist
so you can attach evidence to a support ticket.
Present only while the order is held by someone. Today the only
possible owner is the settlement bank, which is exactly the
information PENDING_APPROVAL fails to convey: when this object is
present there is nothing to approve on your side or on ours.
Transaction counterparty (payer or beneficiary).
Transaction counterparty (payer or beneficiary).
Transaction counterparty (payer or beneficiary).
Balance after transaction (when available).
Linked QR code txid (if transaction from QR code).