---
title: "Get Financial Transaction"
method: GET
path: "/v1/financial-transactions/{id}"
tags: ["Financial Transaction"]
---

# Get Financial Transaction

`GET /v1/financial-transactions/{id}`

Retrieves the details of a financial transaction, including its type, amount, source account, and ownership trace.

## Path parameters

- `id` string, required — Unique identifier of the financial transaction to retrieve.

## Headers

- `Monime-Version` 'caph.2025-08-23' | 'caph.2025-06-20', nullable — Specifies which version of the Monime API will handle this request.
- `Monime-Space-Id` string, required — The value is the tenancy parameter that Monime uses to determine which space the request is intended for.

## Response `200`

OK

- object
  - `success` boolean — Represents the status of the query operation, confirming if it was successful. This field is always true
  - `messages` unknown[] — Contains a list of messages providing relevant information or feedback related to the query or operation
    - unknown
  - `result` FinancialTransaction — A **Financial Transaction** represents a movement of funds that affects a Financial Account, either as a **credit** (inflow) or a **debit** (outflow). Every transaction adjusts the balance of an account and provides a full audit trail of how money moves within Monime. --- ### Use Cases - **Customer Payment Recording** A user pays SLE 500 into your platform via Mobile Money. *Result*: A **credit transaction** is posted to a financial account of the space; this transaction is linked to a **Payment** created from the originating **Payment Code**. - **Fee Deduction** A SLE 50 fee is charged for a payout of SLE 1,000. *Result*: - A **debit transaction** of SLE 1,000 from the payout account. - A **debit transaction** of SLE 50 from the payout account. - **Internal Transfer** Moving SLE 10,000 from a Settlement Account to a Disbursement Float. *Result*: - A **debit transaction** on the Settlement Account. - A **credit transaction** on the Disbursement Float Account. - **Refund or Reversal** If a payment is refunded, a corresponding **debit transaction** reduces the merchant’s balance. *Result*: The audit trail shows both the original credit and the refund debit, linked together. ---
    - `id` string — Unique identifier for this financial transaction.
    - `type` 'credit' | 'debit' — Indicates whether the transaction is a 'credit' or 'debit'.
    - `amount` object — The monetary value involved in this transaction.
      - `currency` string — The [3-letter](https://en.wikipedia.org/wiki/ISO_4217) ISO currency code. Currently supported: 'SLE'
      - `value` integer — The value representation in the currency's minor unit. E.g. For 1 Leone (SLE 1), the value should be 100, denoting cents, the minor unit.
    - `timestamp` string, date-time — The exact time when this transaction was recorded.
    - `reference` string, nullable — Internal identifier associated with this transaction for reconciliation purposes.
    - `financialAccount` object — The account that was debited or credited as part of this transaction, including post-transaction balance snapshot.
      - `id` string — **Account ID**: Unique identifier of the financial account affected by this transaction.
      - `balance` object, nullable — **Account balance**: Balance snapshot of the account immediately after the transaction, if available.
        - `after` object — **Post-transaction balance**: The available balance of the account immediately after this transaction completed.
          - `currency` string — The [3-letter](https://en.wikipedia.org/wiki/ISO_4217) ISO currency code. Currently supported: 'SLE'
          - `value` integer — The value representation in the currency's minor unit. E.g. For 1 Leone (SLE 1), the value should be 100, denoting cents, the minor unit.
    - `originatingReversal` object, nullable — Indicates that this transaction was created as the result of a reversal action. The transaction itself represents the reversal of fund.
      - `originTxnId` string — The ID of the transaction that was reversed by this transaction
      - `originTxnRef` string — The reference of the transaction that was reversed by this transaction
    - `originatingFee` object, nullable — Indicates that this transaction was created as the result of an internal platform fee. The transaction itself represents the fee.
      - `code` string — The type of charge applied.
    - `ownershipGraph` object, nullable — Traceability structure showing which resource or object owns or initiated this transaction.
      - `owner` object — **Immediate object** that owns this entity. This is the direct originator or source object.
        - `id` string — **Unique ID** of the object instance that owns this entity.
        - `type` string — **Type of the object** that owns this entity. Examples include: 'internal_transfer', 'checkout_session', 'payment_code'.
        - `metadata` object, nullable — **Arbitrary metadata** describing the owning object.
        - `owner` CoreresourcesParentOwningObject
          - `id` string — **Unique ID** of the object instance that owns this entity.
          - `type` string — **Type of the object** that owns this entity. Examples include: 'internal_transfer', 'checkout_session', 'payment_code'.
          - `metadata` object, nullable — **Arbitrary metadata** describing the owning object.
          - `owner` CoreresourcesParentOwningObject — recursive
    - `metadata` object, nullable — Custom structured key-value pairs associated with this transaction for additional context.

---

[API](https://skmtc.dev/monime/apis/monime-api.md) · [All operations](https://skmtc.dev/monime/apis/monime-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/monime/monime-api/revisions/bd7f875ea428/schema)