Get transaction by ID
Read one direction-aware public transaction detail by transactionId. This canonical public detail route returns either the Outgoing Transaction or Incoming Transaction variant. For Step 4 incoming review cases, the incoming variant may additionally expose reviewReason, decisionMode, recommendedAction, missingRequiredFields, actionAvailabilityHints, and the bounded scenario detail fields thresholdPolicyNote, sanctionsMatchSummary, or senderComplianceSummary.
Authorizations
Integration-key Basic Auth (clientId:clientSecret) as documented in docs/public/AUTHENTICATION.md.
Path Parameters
Canonical public transaction identifier for this transaction detail route.
Response
Transaction detail returned. The 200 response is direction-aware and may be the Outgoing Transaction or Incoming Transaction variant.
- Option 1
- Option 2
Direction-aware public transaction detail response. The 200 response is either the Outgoing Transaction or Incoming Transaction variant.
Canonical public transaction identifier for this transaction detail response.
Quote identifier associated with the transaction when available.
Direction of this transaction.
OUTGOING Current transaction lifecycle status.
CREATED, PENDING, PROCESSING, COMPLETED, REJECTED, FAILED, REFUNDED, EXPIRED System-generated BLIPS customer identifier associated with this transaction when available.
Platform-side customer identifier associated with this transaction when available.
Transaction creation timestamp.
Last update timestamp.
Settlement timestamp when the transaction has reached a settled terminal state.
Bounded source account detail for the outgoing transaction.
Bounded destination detail for the outgoing transaction.
Main sent amount for the outgoing transaction.
Applied exchange rate when available.
Total fees charged for the transaction when available.