--- 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 details displayed on a receipt. - `transaction_code` string — Transaction code returned after processing the transaction. - `transaction_id` string — Unique identifier of the transaction. - `merchant_code` string — Short unique identifier for the merchant. - `amount` string — Total transaction amount, in major units. - `vat_amount` string — VAT included in the transaction amount, in major units. - `tip_amount` string — Tip included in the transaction amount, in major units. - `currency` string — Three-letter ISO 4217 currency code of the transaction. - `timestamp` string, date-time — The timestamp of when the transaction was created. - `status` string — Current processing status of the transaction. - `payment_type` string — Payment type used for the transaction. - `entry_mode` string — Entry mode of the payment details. - `verification_method` string — Cardholder verification method. - `card_reader` ReceiptReader — Card reader details displayed on the receipt. - `code` string — Unique identifier of the physical card reader. - `type` string — Model of the physical card reader. - `card` ReceiptCard — Payment card details displayed on the receipt. - `last_4_digits` string — Last four digits of the payment card number. - `type` string — Issuing card network of the payment card. - `installments_count` integer — Number of installments. - `process_as` 'CREDIT' | 'DEBIT' — Whether the transaction was processed as credit or debit. - `products` object[] — Products associated with the transaction. - `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 — Total VAT amount for the product quantity. - `quantity` integer — Product quantity. - `total_price` string, double — Total price calculated as the product price multiplied by the quantity. - `total_with_vat` string, double — Total product price including VAT. - `vat_rates` object[] — VAT breakdown for the transaction. - `gross` number, float — Gross amount to which the VAT rate applies. - `net` number, float — Net amount to which the VAT rate applies. - `rate` number, float — VAT rate applied to the transaction amount. - `vat` number, float — VAT amount included in the gross amount. - `events` ReceiptEvent[] — Transaction events displayed on the receipt. - `id` integer — Unique identifier of the transaction event. - `transaction_id` string — Unique identifier 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 associated with the transaction event, in major units. - `timestamp` string, date-time — The timestamp of when the transaction event occurred. - `receipt_no` string — Receipt number associated with the event. - `receipt_no` string — Receipt number associated with the transaction. - `merchant_data` ReceiptMerchantData — Merchant details displayed on a transaction receipt. - `merchant_profile` object — Merchant profile details displayed on the receipt. - `merchant_code` string — Short unique identifier for the merchant. - `business_name` string — Business name of the merchant. - `company_registration_number` string — Company registration number of the merchant. - `vat_id` string — VAT identification number of the merchant. - `website` string — Website of the merchant. - `email` string — Email address of the merchant. - `language` string — Language configured for the merchant profile. - `address` object — Business address of the merchant. - `address_line1` string — First line of the merchant address. - `address_line2` string — Second line of the merchant address. - `city` string — City of the merchant address. - `country` string — Two-letter ISO 3166-1 alpha-2 country code of the merchant address. - `country_en_name` string — English name of the country in the merchant address. - `country_native_name` string — Localized name of the country in the merchant address. - `region_name` string — Region or state of the merchant address. - `post_code` string — Postal code of the merchant address. - `landline` string — Landline phone number of the merchant. - `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 — Identifier of the terminal used for the authorization. - `authorization_code` string — Authorization code returned by the acquirer. - `return_code` string — Return code reported by the acquirer. - `local_time` string — Local timestamp of the card authorization. ## 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/b050b86c35d1/schema)