---
title: "Get transaction and authorization given transactionId"
method: GET
path: "/v3/{id}"
tags: ["Get transaction data"]
---

# Get transaction and authorization given transactionId

`GET /v3/{id}`

This operation will respond with a transaction given transactionId.

## Path parameters

- `id` string, biginteger, required

## Query parameters

- `auditUser` string, required

## Response `200`

Successful lookup of the transaction

- TransactionResponse
  - `id` string — Unique transaction id
  - `linkId` string — Unique Root id for the transaction or Authorization
  - `transactionDate` string, date-time — The local date (and time) when the transaction was made. I.e. the date/time in the time zone in which the payment terminal/merchant is. In date-time format YYYY-MM-DDThh:mm:ss. Please note that the authorisation and clearing formats used by card schemes for do not support conveying the time zone in which the transaction has been done. The card scheme may also just include the date and no specific time. Enfuce relays the date and time as received from the card scheme.
  - `postingDate` string, date-time — The date and time when transaction was posted at Enfuce. In date-time format YYYY-MM-DDThh:mm:ss. Timezone is Enfuce system timezone, i.e. UTC.
  - `postingStatus` 'POSTED' | 'POSTED_DISPUTE' | 'CLOSED' | 'PENDING' | 'REJECTED' — Posting status values: * `POSTED` - Transaction/authorization has been successfully posted. * `POSTED_DISPUTE` - Transaction has been posted with the dispute contract. * `CLOSED` - Authorization status after its matching transaction was successfully processed, or if the authorization is expired. * `PENDING` - Transaction/authorization is waiting for processing or being processed. * `REJECTED` - Transaction/authorization was rejected.
  - `responseCode` string — After authorization, Enfuce generates a response code that guides the merchant how to proceed with the purchase. If approved (Response code 0 or 10), the purchase is finalized. If declined (Response code is not 0 or 10), the merchant must cancel the purchase or request an alternative payment method. Refer to our [service description](https://docs.enfuce.com/guides/the-essentials/global-processing/authorisation-and-authentication-of-payments#authorisation-response) for a complete list of response codes and their usage details. Response code values according to ISO-8583:1987: * Approved: 0 or 10 * Declined: 3-96 and 1A, N0, N7
  - `responseDescription` string — When a payment is declined, a response description is returned, if available, providing more context on why the transaction failed. This includes a return code and a brief explanation. If multiple issues cause the decline, only one response description is sent, prioritized as the most relevant for the decline. Refer to our [service description](https://docs.enfuce.com/guides/the-essentials/global-processing/authorisation-and-authentication-of-payments#understanding-payment-declines) for the list of most relevant response descriptions and their usage details.
  - `transactionType` 'RETAIL' | 'CASH' | 'ATM' | 'CREDIT' | 'UNIQUE' | 'P2P_CREDIT' | 'P2P_DEBIT' | 'BALANCE_INQUIRY' | 'CASH_DISBURSEMENT' — The transaction type. The only fully supported type is RETAIL. Other transaction types may be used, but no guarantees are made about their behaviour. Some transaction types have specific limitations: * `ATM` - In order to create ATM transactions, `merchantData.merchantCategoryCode` must be `6011`. This behaviour is downstream from the VISA and MC authorization systems. If a different code is used, transactions will be treated as `CASH`
  - `transactionConditionCode` string — Transaction conditions define the specific circumstances under which a card transaction occurred. For example, they describe whether the chip was read or if the transaction was contactless, how the cardholder was authenticated, and whether the transaction was e-commerce or card-present. For more information, see our [Transaction Conditions Service Description](https://docs.enfuce.com/guides/the-essentials/global-processing/transaction-conditions).
  - `retrievalReferenceNumber` string — Retrieval reference number
  - `authorizationCode` string — Authorization code
  - `acquiringInstitutionIdentificationCode` string — Acquiring Institution Identification Code
  - `cardAcceptorIdentificationCode` string — Card Acceptor Identification Code
  - `terminalId` string — For authorizations and clearings, this is a unique alphanumeric identifier (typically up to 8–16 characters) used to distinguish a specific physical or virtual payment device, such as a POS machine or ATM, from all others. For other transactions, this refers to the originating source or channel
  - `submerchantId` string — Related to cardAcceptorIdentificationCode, represents sub card acceptor
  - `settlementAmount` SettlementAmount — Settlement amount summed up with markup fee (if markup fee is present).
    - `amount` number
    - `currency` string — A valid ISO 4217 currency code
  - `transactionAmount` Money — Amount including currency
    - `amount` number
    - `currency` string — A valid ISO 4217 currency code
  - `feeAmount` object — Summed up other fees
    - `amount` number
    - `currency` string — A valid ISO 4217 currency code
  - `merchant` Merchant — Will give merchant information if available
    - `id` string
    - `acquirerId` string
    - `country` string — A valid ISO 3166-1 alpha-3 country code, except for QZZ (UNMIK in Kosovo) and ROM for Romania.
    - `city` string
    - `name` string
    - `mcc` string
    - `subMerchantId` string
  - `text` string — Represents value of `text` field provided during transaction posting
  - `paymentReference` string — Reference number used for the transaction
  - `payerName` string — First and last name of payer
  - `paymentReceiver` string — Payment receiver name
  - `fromAddress` string — Address of payer
  - `fromZip` string — Zip code of payer
  - `fromCity` string — City of payer
  - `fromBankAccountNumber` string — Source account number
  - `toBankAccountNumber` string — Target account number
  - `fromCustomerAccountNumber` string — from the Enfuce system, where the payment was posted
  - `fromOrganizationalNumber` string — Send organization number
  - `fromBankName` string — Source bank name
  - `fromBankAccountType` 'BBAN' | 'IBAN' | 'PLUSGIRO' | 'BANKGIRO' — The type of bank account
  - `toBankAccountType` 'BBAN' | 'IBAN' | 'PLUSGIRO' | 'BANKGIRO' — The type of bank account
  - `toBic` string — Target BIC code, used for pain file generation
  - `discLinkTransactionId` string — The transactionId of the original financial transaction of this discount
  - `createdAt` string, date-time — The date and time in YYYY-MM-DDThh:mm:ss format when transaction was created. Timezone is Enfuce system timezone, i.e. UTC.
  - `fileName` string — Name of processed file, typically for managing incoming payments.
  - `processedByEnfuceStip` boolean — For authorizations, indicates whether authorization was processed by Enfuce STIP or not.
  - `receivedFromCollectionAgency` boolean — Whether a collection payment transaction (CPT) is received from a collection agency or not. Only applies to payment transactions for invoices in collection.
  - `acqRefNumber` string — Acquirer Reference Number (ARN) is a unique number assigned to a card transaction by the acquirer (merchant's bank). It is used to track a specific transaction across banks (merchant bank, cardholder bank, etc.).
  - `authValidityInDays` integer — Specifies the number of days the authorisation is valid when longer than the default (7 days). If not provided, the default authorisation validity period applies.
  - `exchangeRate` string — Exchange rate used for the transaction.
  - `unit` string — Unit of measure if available
  - `siteCountry` string — Site country code
  - `transSrn` string — Enfuce NDU Transaction SRN
  - `enfuceNduId` string — Enfuce NDU transaction id
  - `accountId` string — AccountId transaction is posted to
  - `cardId` string — If transaction is posted to a card then this cardId will be set
  - `lineItems` LineItems[]
    - `id` string — Unique transaction id
    - `enfuceNduLineItemId` string — Internal reference ID assigned to a parsed line item record from the NDU file.
    - `productCode` string — Product code from external system
    - `productDescription` string — Product description
    - `discountAmount` number — Discount amount
    - `quantity` number — Quantity of products
    - `unit` string — Units of measure of products
    - `posProductSubGroup` string — Product subgroup from POS system
    - `productGroupPosToFep` string — Product group mapping from POS to FEP
    - `totalNetAmount` number — Total net amount after discount, excluding VAT amount
    - `perUnitGrossAmount` number — Gross amount per unit
    - `perUnitGrossDiscountAmount` number — Gross discount amount per unit
    - `siteCountry` string — Site country code
    - `transSrn` string — Enfuce NDU Transaction SRN
    - `exchangeRate` string — Exchange rate used for the line item.
    - `vatAmount` number — The total VAT amount after discount
    - `vatRate` number — The VAT percentage
    - `programId` string — Program id

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `404` — Transaction does not exist
- `500` — Internal server error

---

[API](https://skmtc.net/enfuce/apis/transfer-api.md) · [All operations](https://skmtc.net/enfuce/apis/transfer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/enfuce/transfer-api/versions/dc4a41118f80/schema)