---
title: "Retrieve receipt details"
method: GET
path: "/v1.1/receipts/{transaction_id}"
tags: ["Receipts"]
---

# Retrieve receipt details

`GET /v1.1/receipts/{transaction_id}`

Retrieves receipt specific data for a transaction.

## Path parameters

- `transaction_id` string, required

## Query parameters

- `mid` string, required
- `tx_event_id` integer

## Response `200`

Returns receipt details for the requested transaction.

- Receipt — Receipt details for a transaction.
  - `transaction_data` ReceiptTransaction — Transaction information.
    - `transaction_code` string — Transaction code.
    - `transaction_id` string — Unique ID of the transaction.
    - `merchant_code` string — Merchant code.
    - `amount` string — Transaction amount.
    - `vat_amount` string — Transaction VAT amount.
    - `tip_amount` string — Tip amount (included in transaction amount).
    - `currency` string — Transaction currency.
    - `timestamp` string, date-time — Time created at.
    - `status` string — Transaction processing status.
    - `payment_type` string — Transaction type.
    - `entry_mode` string — Transaction entry mode.
    - `verification_method` string — Cardholder verification method.
    - `card_reader` ReceiptReader — Card reader details displayed on the receipt.
      - `code` string — Reader serial number.
      - `type` string — Reader type.
    - `card` ReceiptCard — Payment card details displayed on the receipt.
      - `last_4_digits` string — Card last 4 digits.
      - `type` string — Card Scheme.
    - `installments_count` integer — Number of installments.
    - `process_as` 'CREDIT' | 'DEBIT' — Debit/Credit.
    - `products` object[] — Products
      - `name` string — Product name
      - `description` string — Product description
      - `price` string, double — Product price
      - `vat_rate` string, double — VAT rate
      - `single_vat_amount` string, double — VAT amount for a single product
      - `price_with_vat` string, double — Product price including VAT
      - `vat_amount` string, double — VAT amount
      - `quantity` integer — Product quantity
      - `total_price` string, double — Quantity x product price
      - `total_with_vat` string, double — Total price including VAT
    - `vat_rates` object[] — Vat rates.
      - `gross` number, float — Gross
      - `net` number, float — Net
      - `rate` number, float — Rate
      - `vat` number, float — Vat
    - `events` ReceiptEvent[] — Events
      - `id` integer — Unique ID of the transaction event.
      - `transaction_id` string — Unique ID of the transaction.
      - `type` 'PAYOUT' | 'CHARGE_BACK' | 'REFUND' | 'PAYOUT_DEDUCTION' — Type of the transaction event.
      - `status` 'FAILED' | 'PAID_OUT' | 'PENDING' | 'RECONCILED' | 'REFUNDED' | 'SCHEDULED' | 'SUCCESSFUL' — Status of the transaction event. Not every value is used for every event type. - `PENDING`: The event has been created but is not final yet. Used for events that are still being processed and whose final outcome is not known yet. - `SCHEDULED`: The event is planned for a future payout cycle but has not been executed yet. This applies to payout events before money is actually sent out. - `RECONCILED`: The underlying payment has been matched with settlement data and is ready to continue through payout processing, but the funds have not been paid out yet. This applies to payout events. - `PAID_OUT`: The payout event has been completed and the funds were included in a merchant payout. - `REFUNDED`: A refund event has been accepted and recorded in the refund flow. This is the status returned for refund events once the transaction amount is being or has been returned to the payer. - `SUCCESSFUL`: The event completed successfully. Use this as the generic terminal success status for event types that do not expose a more specific business outcome such as `PAID_OUT` or `REFUNDED`. - `FAILED`: The event could not be completed. Typical examples are a payout that could not be executed or an event that was rejected during processing.
      - `amount` string, double — Amount of the event.
      - `timestamp` string, date-time — Date and time of the transaction event.
      - `receipt_no` string — Receipt number associated with the event.
    - `receipt_no` string — Receipt number
  - `merchant_data` ReceiptMerchantData — Receipt merchant data
    - `merchant_profile` object — Merchant profile details displayed on the receipt.
      - `merchant_code` string
      - `business_name` string
      - `company_registration_number` string
      - `vat_id` string
      - `website` string
      - `email` string
      - `language` string
      - `address` object
        - `address_line1` string
        - `address_line2` string
        - `city` string
        - `country` string
        - `country_en_name` string
        - `country_native_name` string
        - `region_name` string
        - `post_code` string
        - `landline` string
    - `locale` string — Locale used for rendering localized receipt fields.
  - `emv_data` object — EMV-specific metadata returned for card-present payments.
  - `acquirer_data` object — Acquirer-specific metadata related to the card authorization.
    - `tid` string
    - `authorization_code` string
    - `return_code` string
    - `local_time` string

## Other responses

- `400` — The request is invalid for the submitted parameters.
- `401` — The request is not authorized.
- `404` — The requested transaction event does not exist for the provided transaction.

---

[API](https://skmtc.net/sumup/apis/sumup-rest-api.md) · [All operations](https://skmtc.net/sumup/apis/sumup-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sumup/sumup-rest-api/revisions/f50e1dc97523/schema)