---
title: "Get transaction"
method: GET
path: "/v2/transactions/{transactionId}"
tags: ["Transactions"]
---

# Get transaction

`GET /v2/transactions/{transactionId}`

## Request

- Base URL: `https://sandbox.pismolabs.io/transactions-core`
- URL: `https://sandbox.pismolabs.io/transactions-core/v2/transactions/{transactionId}`
- Auth: HTTP bearer

Get a specific transaction by its ID. You can use the [List transactions](ref:searchtransactions) endpoint to search for a transaction and get its ID.

## Path parameters

- `transactionId` integer, required

## Query parameters

- `includeMetadata` boolean

## Response `200`

OK

- TransactionWithMetadata
  - `id` integer: Transaction ID
  - `program_id` integer: Program ID
  - `account_id` integer: Account ID
  - `statement_id` integer: Statement ID
  - `installment` integer: Transaction installment number
  - `number_of_installments` integer: Total number of installments
  - `soft_descriptor` string: Soft descriptor of transaction. This is the description that shows on the customer's statement after it is authorized, but before it is settled.
  - `processing_code` string: Processing code used to create the transaction.
  - `processing_description` string: Processing code description
  - `customer_id` integer: Customer ID
  - `user_category` string: User category
  - `transaction_group` string: Transaction group
  - `entry_mode` string: Transaction Entry Mode
  - `amount` Amount[]
    - `type` 'PRINCIPAL' | 'LOCAL' | 'SETTLEMENT': Amount type - `PRINCIPAL`: Transaction amount in the customer’s account currency (already converted). - `LOCAL`: Transaction amount in the merchant’s local currency, where the purchase was made. - `SETTLEMENT`: Settlement amount that is typically defined by the issuer and usually matches the `PRINCIPAL` currency.
    - `currency` string: ISO-4217 alphabetic code (3 characters) for transaction currency.
    - `value` number: Amount value
  - `tax` Tax[]: Transaction taxes
    - `currency` string: ISO-4217 alphabetic code (3 characters) for transaction currency.
    - `type` 'IOF' | 'IOF_DAILY' | 'INTEREST': Tax type
    - `value` number: Tax value
  - `event_date` string, date-time: Event timestamp in the UTC (zero-hour offset) ISO 8601 format (yyyy-MM-ddThh:mm:ssZ).
  - `event_datetime` string, date-time: Event timestamp in the UTC (zero-hour offset) RFC 3339 format, which includes milliseconds (yyyy-MM-ddThh:mm:ss.SSSZ).
  - `payment_date` string, date-time: Payment timestamp provided by the user in the ISO 8601 format (yyyy-MM-ddThh:mm:ssZ).
  - `payment_datetime` string, date-time: Payment timestamp provided by the user in the RFC 3339 format, which includes milliseconds (yyyy-MM-ddThh:mm:ss.SSSZ).
  - `created_at` string, date-time: Transaction creation date (ISO 8601)
  - `transaction_type` TransactionType
    - `id` integer: Transaction type ID
    - `description` string: Transaction type description
    - `credit` boolean: Indicates if the transaction type is a credit or debit operation.
    - `posted_transaction` boolean: Indicates whether transactions are posted on statements (`true`) or not (`false`).
    - `balance_impact_id` integer: Balance impact ID
    - `category` string: Transaction type category
  - `card` Card: Contains details about the card used in a transaction. * For transactions from card network operations, this object includes card information. * For platform operations, this object is empty. Whether card information appears depends on what was provided during authorization, not on the transaction type.
    - `id` integer: Card ID
    - `name` string: Card name
  - `authorization` Authorization
    - `id` integer: Authorization ID
    - `type` 'PLATFORM' | 'NETWORK': Authorization's type
    - `code` string: Authorization code or Network Approval Code
    - `payment_method_id` string: Payment method
    - `network` 'VISA' | 'MASTERCARD': Visa or Mastercard network
    - `tracking_id` string: Idempotency tracking ID
    - `correlated_authorization_id` integer: Authorization ID generated by force or installment operations when the `original_authorization` field is provided. See the [Force operation](doc:force-operation) and [Installments payment](doc:installments-payment) guides for more information.
    - `original_account_id` integer: Original account ID. This field is used when the transaction is linked to a authorizaiton that was made on a different account than the one being queried.
  - `merchant` Merchant
    - `id` string: Merchant ID
    - `type` string: Merchant type
    - `name` string: Merchant name
    - `city` string: Merchant city
    - `state` string: Merchant's state. In some cases, for countries other than the U.S., it can indicate the country code of the merchant instead.
    - `category` MerchantCategory
      - `code` string: Merchant category code (MCC). Provided by the network (Visa or Mastercard).
      - `description` string: Merchant category description
      - `group_name` string: Merchant category group name
      - `network_group` string: Merchant category group name sent by network
  - `metadata` object: This optional user-defined key-value object field can be used with external operations to provide additional context or supplementary custom information for the operation. The Pismo platform does not perform any validation or processing on this field. **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](ref:get-started-with-pismo-apis#metadata).

## Other responses

- `400`: Bad request
- `404`: Not found
- `500`: Internal error

---

[API](https://skmtc.dev/pismo/apis/core-platform-transactions.md) - [All operations](https://skmtc.dev/pismo/apis/core-platform-transactions/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/core-platform-transactions/revisions/0446e20d4547?raw)