Get transaction details
Retrieve detailed information about a specific transaction by its external ID.
Returns complete transaction data including:
- Transaction metadata (type, status, direction, amount)
- Associated asset information (symbol, decimals, chain)
- Related entities when applicable (wallet, bank account, card)
- Merchant details for card transactions (name, category, MCC)
- On-chain data for crypto transactions (tx_hash)
Authorization: Only the owning user can access their transactions. Returns 403 Forbidden if the transaction belongs to a different user.
Authorizations
PINT (Purchase Intent) token — a JWT issued via POST /v0/sis/token/pint that encodes user-level consent for a specific scope. Sent in the x-sumvin-pint-token header alongside or instead of an x-juno-jwt JWT, depending on the integration surface (Platform vs SIS).
Headers
Tenant org ID for multi-tenant auth
Controls how timestamp fields are serialized in JSON response bodies.
Default (header omitted or any other value): epoch milliseconds as integers.
iso8601: UTC ISO 8601 strings of the form YYYY-MM-DDTHH:MM:SSZ.
Example: with X-Timestamp-Format: iso8601, the field value 1704067200000 becomes "2024-01-01T00:00:00Z".
Affected fields (recursively, in dicts and arrays): any field whose name ends in _at, plus the literal field names timestamp, period_start, and period_end. All other fields are passed through unchanged.
Only iso8601 is recognized. Any other value (or omitting the header) yields the default epoch-ms representation; the server does not reject unknown values, so this is documented as an example rather than an enum to keep generated clients permissive.
"iso8601"
Path Parameters
Response
Transaction retrieved successfully
Detailed transaction response with full entity data.
HAL-style hypermedia links for navigation.
Unique transaction identifier
Transaction type (deposit, withdrawal, card_purchase, etc.)
Transaction status (pending, processing, completed, failed)
Fund flow direction relative to user (in, out)
Transaction amount in asset's base units
^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$Transaction creation timestamp (epoch ms)
Last update timestamp (epoch ms)
Funding source (crypto_wallet, bank_account, card)
Asset involved in the transaction, when known
Wallet for crypto transactions
Bank account for bank transactions
Card for card transactions
On-chain transaction hash (crypto only)
Merchant name (card/bank transactions)
4-digit ISO 18245 merchant category code
Spending category (restaurants, groceries, etc.)
External processor transaction reference
Whether this transaction has an attached receipt