---
title: "Fetch transaction metadata"
method: GET
path: "/transactions/info"
tags: ["Transactions"]
---

# Fetch transaction metadata

`GET /transactions/info`

Get transaction details by `id`, `foreign_id`, or `txid`. Include only one of these parameters in your request.

## Headers

- `X-Processing-Signature` string, required

## Request body

- union
  - object
    - `id` integer, required — Internal transaction ID.
  - object
    - `foreign_id` string, required — The transaction's unique identifier in your system. You can only find withdrawal transactions by their foreign_id. For deposits, search by id.
  - object — Transaction hash.
    - `txid` string, required

## Response `200`

OK

- object
  - `id` integer, required
  - `foreign_id` string — This transaction's unique identifier in your system.
  - `end_user_reference` string — End user reference. Present only when KYC data was provided.
  - `type` string, required — Transaction type.
  - `crypto_address` object — Address details. Present only when entry has an associated address.
    - `id` integer, required
    - `currency` string, required — Currency ISO code.
    - `convert_to` string — Conversion target currency. Present only when address has conversion logic.
    - `address` string, required
    - `tag` string, nullable, required
    - `foreign_id` string
  - `currency_sent` object — Sent currency details. Present for confirmed, verifying, or processing transactions.
    - `currency` string, required — Currency ISO code.
    - `amount` string, required — Amount sent.
  - `currency_received` object — Received currency details. Present for confirmed, verifying, or processing transactions.
    - `currency` string, required — Currency ISO code.
    - `amount` string, required — Amount received.
    - `amount_minus_fee` string — Amount received minus fees. Present only for deposit transactions.
  - `transactions` object[], required — Transaction entries. Each entry has a `transaction_type` that determines which fields are present: - `blockchain`: On-chain transactions (has address, tag, txid, riskscore, confirmations) - `internal`: Internal transfers (has address, tag, txid, confirmations) - `exchange`: Currency exchanges (has currency_to, amount_to)
    - `id` integer, required
    - `currency` string, required — Currency ISO code.
    - `currency_to` string — Destination currency. Present only for `exchange` entries.
    - `transaction_type` 'blockchain' | 'internal' | 'exchange', required
    - `type` string, required — Entry type (e.g., deposit, withdrawal).
    - `address` string — Cryptocurrency address. Present for `blockchain` and `internal` entries.
    - `tag` string, nullable — Destination tag. Present for `blockchain` and `internal` entries.
    - `amount` string, required — Transaction amount.
    - `amount_to` string — Amount in destination currency. Present only for `exchange` entries.
    - `txid` string, nullable
    - `riskscore` string, nullable — Risk score (0-100). Present only for `blockchain` entries when risk scoring is enabled.
    - `confirmations` string — Number of blockchain confirmations. Present for `blockchain` and `internal` entries.
  - `fees` object[], required
    - `type` string, required — Fee type identifier (e.g., `mining`, `fee_crypto_withdrawal`, etc.).
    - `currency` string, required — Fee currency ISO code.
    - `amount` string, required — Fee amount. Returns '0' when system pays network fees.
  - `error` string, nullable — Error message. Null or empty string for successful transactions.
  - `status` 'cancelled' | 'confirmed' | 'declined' | 'not_confirmed' | 'pending', required — Transaction status. Note: internal statuses are mapped before returning: - `processing` and `verifying` are returned as `not_confirmed` - `error` is returned as `cancelled` - `rejected` is returned as `cancelled`
  - `additional_details` object, nullable — Additional transaction details. Present only when available.

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `404` — Transaction not found

---

[API](https://skmtc.dev/cryptoprocessing/apis/merchant-backend-v2.md) · [All operations](https://skmtc.dev/cryptoprocessing/apis/merchant-backend-v2/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/cryptoprocessing/merchant-backend-v2/revisions/623a41f26c6b/schema)