---
title: "Retrieves a list of transactions."
method: GET
path: "/admin/orders/{order_id:(?:\\\\d+)}/transactions.json"
tags: ["Transaction"]
---

# Retrieves a list of transactions.

`GET /admin/orders/{order_id:(?:\\d+)}/transactions.json`

Transactions attached to multi-currency orders are in the presentment currency by default. To retrieve transactions in the shop currency, include the URL parameter in_shop_currency=true.

## Query parameters

- `since_id` number
- `fields` string
- `in_shop_currency` boolean

## Response `200`

OK

- OrderTransactionsSwaggerResponse
  - `transactions` TransactionDto[]
    - `amount` number — The amount of money included in the transaction. If you don't provide a value for `amount`, then it defaults to the total cost of the order (even if a previous transaction has been made towards it).
    - `authorization` string — The authorization code associated with the transaction.
    - `conversion_rate` number
    - `created_at` string — The date and time ([ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601)) when the transaction was created.
    - `currency` string — The three-letter code ([ISO 4217 format](https://en.wikipedia.org/wiki/ISO_4217)) for the currency used for the payment.
    - `currency_exchange_adjustment` CurrencyExchangeAdjustmentDto
      - `adjustment` number — The difference between the amounts on the associated transaction and the parent transaction.
      - `currency` string — The shop currency.
      - `final_amount` number — The amount of the associated transaction in the shop currency.
      - `id` integer — The ID of the adjustment.
      - `original_amount` number — The amount of the parent transaction in the shop currency.
    - `device_id` integer — The ID for the device.
    - `error_code` unknown
    - `gateway` string — The name of the gateway the transaction was issued through.
    - `id` integer — The ID for the transaction.
    - `kind` string — The transaction's type. Valid values * **authorization**: Money that the customer has agreed to pay. The authorization period can be between 7 and 30 days (depending on your payment service) while a store waits for a payment to be captured. * **capture**: A transfer of money that was reserved during the authorization of a shop. * **sale**: The authorization and capture of a payment performed in one single step. * **void**: The cancellation of a pending authorization or capture. * **refund**: The partial or full return of captured money to the customer.
    - `location_id` integer — The ID of the physical location where the transaction was processed.
    - `message` string — A string generated by the payment provider with additional information about why the transaction succeeded or failed.
    - `order_id` integer — The ID for the order that the transaction is associated with.
    - `parent_id` integer — The ID of an associated transaction.
    - `payment_details` PaymentDetailsDto
      - `avs_result_code` string — The response code from the [address verification system](https://en.wikipedia.org/wiki/Address_Verification_System). The code is a single letter; see [this chart](http://www.emsecommerce.net/avs_cvv2_response_codes.htm) for the codes and their definitions.
      - `credit_card_bin` string — The [issuer identification number](https://en.wikipedia.org/wiki/ISO/IEC_7812) (IIN), formerly known as bank identification number (BIN) of the customer's credit card. This is made up of the first few digits of the credit card number.
      - `credit_card_company` string — The name of the company that issued the customer's credit card.
      - `credit_card_number` string — The customer's credit card number, with most of the leading digits redacted.
      - `cvv_result_code` string — The response code from the credit card company indicating whether the customer entered the [card security code](https://en.wikipedia.org/wiki/Card_security_code), or card verification value, correctly. The code is a single letter or empty string; see [this chart](http://www.emsecommerce.net/avs_cvv2_response_codes.htm) for the codes and their definitions.
    - `processed_at` string — The date and time ([ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601)) when a transaction was processed. This value is the date that's used in the analytic reports. By default, it matches the created_at value. If you're importing transactions from an app or another platform, then you can set processed_at to a date and time in the past to match when the original transaction was processed.
    - `receipt` object — A transaction receipt attached to the transaction by the gateway. The value of this field depends on which gateway the shop is using.
    - `source_name` string — The origin of the transaction. This is set by ShopBase and can't be overridden. Example values: web, pos, iphone, and android.
    - `status` string — The status of the transaction. Valid values: `pending`, `failure`, `success`, and `error`
    - `test` boolean — Whether the transaction is a test transaction.
    - `transaction_amount` number — The amount of money included in the payment gateway's transaction.
    - `transaction_currency` string — The three-letter code ([ISO 4217 format](https://en.wikipedia.org/wiki/ISO_4217)) for the payment provider's transaction currency used for the payment.
    - `updated_at` string — The date and time ([ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601)) when the transaction was updated.

---

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