---
title: "Retrieve a single transaction"
method: GET
path: "/transactions/{id}"
tags: ["Endpoints"]
---

# Retrieve a single transaction

`GET /transactions/{id}`

Returns single Transaction for the given unique ID

## Path parameters

- `id` string, required — Unique system identifier of the record in our system.

## Response `200`

OK

- Transaction — A transaction record is created for every cleared authorisation, and indicates that money is ready to be moved (from consumer to merchant) for that payment.
  - `id` string, required — Unique system identifier of the record in our system.
  - `posted` string, date-time, required — The date and time (in ISO 8601 format `yyyy-MM-ddTHH:mm:ssZ`) the clearing message was sent for the transaction.
  - `authorised` string, date-time — The date and time (in ISO 8601 format `yyyy-MM-ddTHH:mm:ssZ`) the authorisation occurred, relative to the terminal location.
  - `status` 'CLEARED' | 'REJECTED' | 'PENDING', required — Whether the transaction has yet been cleared or rejected.
  - `type` 'PURCHASE' | 'PAYMENT' | 'CASH_ADVANCE' | 'REFUND' | 'PURCHASE_WITH_CASHBACK' | 'CARD_VERIFICATION' | 'PREPAID_LOAD' | 'BALANCE_ENQUIRY' | 'CHECK_VERIFICATION' | 'CHECK_GUARANTEE' | 'PURCHASE_ADJUSTMENT' | 'MOBILE_TOPUP' | 'PURCHASE_WITH_TIP' | 'ADMIN' | 'ACCOUNT_FUNDING_TRANSACTION' | 'ORIGINAL_CREDIT' | 'MONEY_TRANSFER', required — The nature of the transaction, which often signifies how it is processed. The most common type is a purchase (the transfer of money for goods or services), but may refer to things like a refund or card verification.
  - `channel` 'ECOMMERCE' | 'POINT_OF_SALE' | 'PAY_BY_LINK' | 'MAIL_ORDER' | 'TELEPHONE_ORDER', required — A categorisation for the system which generated the transaction record. The most common being point of sale (such as an in-store card payment) or ecommerce (via an online store), but also includes channels like pay by link, mail order and telephone order.
  - `merchant` object, required — A merchant is the business entity that the transaction was performed at.
    - `id` string, required — External merchant id provided by client (if merchant ids have been pre allocated) or generated by our systems during merchant boarding.
    - `name` string — Trade name of the merchant, often printed on a card receipt.
    - `countryCode` string, nullable, required — The Alpha 3 ISO location of the merchant.
    - `mcc` string, nullable, required — A [Merchant Category Code (MCC)](https://en.wikipedia.org/wiki/Merchant_category_code) is assigned to each merchant by an acquirer. It classifies the merchant based on the type of goods or services provided, as each industry has different transaction patterns and differing levels of fraud risk. **Examples:** | Code | Description | |---|---| | 0742 | Veterinary Services | | 0763 | Agricultural Co-operatives | | 1520 | General Contractors - Residential and Commercial | For a **full list** of example values, see our [reference guide](https://docs.fiserv.dev/public/docs/merchant-category-codes).
    - `allianceCode` string, nullable, required — An alliance is typically an organization holding an acquiring licence issued by card schemes (like VISA, MasterCard etc). This code is assigned by us.
    - `partnerCode` string, nullable — Partners are typically companies (such as Payment Facilitators, Independent Software Vendors, Independent Sale Organisations) who can contract merchants for card acceptance but they don't hold an acquiring licence so must always be authorized by an Alliance.
    - `storeId` string, nullable — A digital store id assigned in our payment gateway. The store holds configuration such as what payment methods are accepted.
  - `meta` object, required — Reference metadata used by both the merchant and acquirer to link the transaction to other records or systems.
    - `orderId` string, nullable — Unique ID of the end-to-end sale which can link together multiple authorisation or cleared transaction records.
    - `authorisationCode` string — 6-digit code returned by the issuer responsible for approving the authorisation in the event that it is approved. Can be used along with other metadata to reference the authorisation, such as in the case of a dispute.
    - `fundingDetailId` string — The unique ID of the specific funding detail row linked to this transaction.
    - `retrievalReferenceNumber` string, nullable — 12 digit reference number following ISO 8583 which can be used with other key data elements to identify and track all messages related to a given transaction. It is usually assigned by the acquirer, but it may be assigned by a merchant or by an individual electronic terminal.
    - `originalReference` string, nullable — Optional reference to the original transaction record, in the case of reject that was re-processed.
    - `terminalBatchNumber` string, nullable — Clearing batch number defined by the terminal that posted the transaction for clearing.
    - `merchantTransactionReference` string, nullable — Flexible reference field provided by the merchant via our payment gateway, usually something that is printed on the receipt and uniquely references the transaction in the merchants system.
    - `acquirerReferenceNumber` string, nullable — Also known as 'ARN', an industry standard unique reference number that can be used to trace a transaction between acquirer and issuer. Useful in cases of refund processing.
  - `paymentInstrument` union, required — The instrument used to make the payment, which will be one of a few specific categories. For more details see our page on [payment types](https://docs.fiserv.com/docs/general/ZG9jOjI2NjE5MjE0-payment-types).
    - object — Basic payment instrument parent
      - `category` 'CARD' | 'CASH' | 'ALTERNATIVE', required — The discriminator used to determine the payment category and object type. For more details see our page on [payment instruments](https://docs.fiserv.dev/public/docs/payment-instruments).
      - `brand` 'AMEX' | 'CUP' | 'DINERS' | 'GIRO' | 'JCB' | 'MAESTRO' | 'MC' | 'PAGO' | 'PP' | 'PRIV' | 'VISA' | 'VPAY' | 'GIFT' | 'C_EGIFT' | 'CARTBLANC' | 'RUPAY', required — The brand or scheme of payment card.
      - `number` string, required — Masked instrument number or account number used to pay for goods or services such as a PAN, PayPal account reference, bank account number. With first 6 and last 4 digits visible in the clear.
      - `subType` string, nullable — Additional information about the type of instrument, for example card products such as Visa Select (N2) and MasterCard Platinum (MPL).
    - object — Basic payment instrument parent
      - `category` 'CARD' | 'CASH' | 'ALTERNATIVE', required — The discriminator used to determine the payment category and object type. For more details see our page on [payment instruments](https://docs.fiserv.dev/public/docs/payment-instruments).
    - object — Basic payment instrument parent
      - `category` 'CARD' | 'CASH' | 'ALTERNATIVE', required — The discriminator used to determine the payment category and object type. For more details see our page on [payment instruments](https://docs.fiserv.dev/public/docs/payment-instruments).
      - `service` 'BLIK' | 'ELV' | 'IDEAL' | 'KLARNA' | 'PAYPAL' | 'PBL' | 'SEPADD' | 'SOFORT' | 'TOPUP' | 'EASYCASH' | 'VIPP' | 'MOBILEPAY' | 'TWINT' | 'SWISH' | 'ALIPAY' | 'WECHATPAY' | 'POSTFINANCE' | 'OTHER', required — Name of the APM (Alternative Payment Method) service used for the payment.
      - `number` string — Masked instrument number or account number used to pay for goods or services such as a PAN, PayPal account reference, bank account number. With first 6 and last 4 digits visible in the clear.
  - `financial` object, required — Financial details for the transaction, such as amounts and fees
    - `amounts` object — Currency amounts relating to the transaction
      - `currencyCode` string, nullable — Base currency for the amounts listed in ISO 4217 format
      - `transacted` string — Amount transacted between cardholder and merchant
      - `cashback` string, nullable — Amount of cashback included in the transaction
      - `tip` string, nullable — Amount of tip included in the transaction
    - `fees` object[] — The fees or charges associated with this cleared transaction, such as merchant service charge or network interchange fee.
      - `type` string, required — The type of fee or charge, such as `INTERCHANGE` or `MERCHANT_SERVICE_CHARGE`
      - `currencyCode` string, nullable — [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) currency code.
      - `amount` string, required — The fee amount, shown as a **positive** currency amount. This may be a fractional currency value of up to 5 decimal places.
    - `funding` object — Detail about the funding relevant to this transaction.
      - `currencyCode` string, nullable — Currency for funding amountsfor the amounts listed in ISO 4217 format
      - `gross` string, nullable — The gross amount to be funded for the transaction before any fees
      - `charges` string, nullable — The total amount of fees deducted from this transaction for funding, shown as a positive amount
      - `net` string, nullable — The final net amount to be funded for the transaction
  - `captureEnvironment` object — Detail about the environment used to capture the payment, such as a terminal.
    - `platform` string, nullable — System which processed the transaction for clearing.
    - `captureMethod` 'ECOMMERCE' | 'CHIP' | 'CHIP_CONTACTLESS' | 'CHIP_UNRELIABLE' | 'MAGNETIC' | 'MAGNETIC_CONTACTLESS' | 'MAGNETIC_UNREADABLE' | 'MAGNETIC_FALLBACK' | 'MANUAL_ENTRY' | 'OCR' | 'UNKNOWN', nullable — The method for which the payment instrument details were captured.
    - `threeDS` 'NON_3DS' | 'MERCHANT_3DS' | 'FULL_3DS' | 'MERCHANT_UCAF' | 'MASTERPASS_MASTERCARD_DECISION' | 'MASTERPASS_ISSUER_DECISION' | 'MASTERPASS_MERCHANT_DECISION' | 'REMOTE_PAYMENT', nullable — Represents the level of security used for an ecommerce transaction. 3-D Secure, also known as payer authentication, is a security protocol that helps to prevent fraud in online credit and debit card transactions by asking the user to provide authentication approval. The decision for approving the transaction based on this data may be made by the merchant or the issuer / card schemes or both (which is referred to as full). The important note being that a party that approves the transaction on this basis accepts liability.
    - `terminal` object
      - `id` string, nullable — Terminal ID is the number assigned to the POI and used between POI and Central Acceptance Host and displayed on terminal and used for reconciliation purposes.
  - `_links` object — HAL-style links to other related resources within our APIs
    - `authorisations` object — A reference to the `/authorisations` endpoint for any authorisation records related to the current transaction, using the following params: - `orderId` field from the current transaction - `createdAfter` the current `authorised` date - `createdBefore` the current `posted` date
      - `href` string
    - `fundings` object — A reference to the `/fundings` endpoint for any funding records related to the current transaction, using the following params: - `fundingDetailId` field from the current transaction - `fundedAfter` the current `posted` date - `fundedBefore` the current date
      - `href` string

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `429` — Too Many Requests
- `500` — Internal server error

---

[API](https://skmtc.net/fiserv/apis/acquirer-profile-in-design.md) · [All operations](https://skmtc.net/fiserv/apis/acquirer-profile-in-design/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fiserv/acquirer-profile-in-design/versions/dd7ef6ce81a1/schema)