---
title: "Retrieve card transactions"
method: GET
path: "/customers/{customerID}/card_accounts/{cardAccountID}/transactions"
tags: ["Cards"]
---

# Retrieve card transactions

`GET /customers/{customerID}/card_accounts/{cardAccountID}/transactions`

Retrieve completed card transactions and card-related crypto transaction activities

## Path parameters

- `customerID` string, required — A UUID that uniquely identifies a resource
- `cardAccountID` string, required — A UUID that uniquely identifies a resource

## Query parameters

- `limit` integer
- `starting_time` string
- `ending_time` string
- `page_size` string
- `page` string
- `status` string[]
- `pagination_token` string
- `category_family` 'cards' | 'crypto'

## Response `200`

Card transactions

- object
  - `page` integer, required — The current page number, starting at 1. Note that this will be returned only for navigating posted transactions.
  - `pagination_token` string — The pagination token to be used to retrieve the next page of transactions. If not provided, use the `page` parameter to navigate by page number.
  - `count` integer, required — The number of transactions returned
  - `total_pages` integer, required — The total number of pages
  - `total_count` integer, required — The total number of transactions
  - `data` CardTransaction[], required
    - `id` string, required — A UUID that uniquely identifies a resource
    - `card_account_id` string — A UUID that uniquely identifies a resource
    - `customer_id` string — A UUID that uniquely identifies a resource
    - `category` 'adjustment' | 'fee' | 'purchase' | 'refund' | 'crypto_funding' | 'crypto_return' | 'crypto_withdrawal', required — The category of the transaction
    - `amount` string, required — The amount represented as a decimal string
    - `billing_amount` string — The billing amount, represented as a decimal string. The billing amount is the amount of the transaction excluding any additional hold. This amount should be present on all purchases, but will only differ from the amount field for some merchant categories in which an upcharge is involved (e.g. gas stations, hotels).
    - `currency` 'usd' | 'usdc', required — The currency of the transaction
    - `merchant_category_code` string — The merchant category code, if applicable (e.g., '5712'). Always returned for transactions with category `purchase` or `refund`
    - `merchant_name` string — The merchant name, if applicable. Always returned for transactions with category `purchase` or `refund`
    - `merchant_location` string — The merchant location, if applicable. Always returned for transactions with category `purchase` or `refund`
    - `description` string, required — The transaction description. It includes the merchant's name and location information for card transactions
    - `local_transaction_details` CardLocalTransactionDetails — Details of a transaction processed in a local currency other than USD, with currency conversion applied
      - `amount` string, required — The amount in local currency, represented as a decimal string
      - `currency` string, required — The transaction's local currency
      - `exchange_rate` string, required — The exchange rate applied to convert the local currency amount into USD for the transaction
    - `posted_at` string, required — Timestamp when the transaction was posted, in ISO8601 format
    - `authorized_at` string — Timestamp when the transaction was authorized, in ISO8601 format. Applicable only to transactions with category `purchase` or `refund` and always returned when applicable
    - `status` 'pending' | 'posted' — The status of the transaction
    - `crypto_transaction_details` CardCryptoTransactionDetails — Details of the underlying crypto transaction for crypto funding, withdrawal, or return transactions
      - `from_address` string — The source blockchain address of the crypto transaction. Present for crypto funding transactions
      - `to_address` string — The destination blockchain address of the crypto transaction
      - `tx_hash` string — The blockchain transaction hash
      - `chain` 'arbitrum' | 'avalanche_c_chain' | 'base' | 'ethereum' | 'optimism' | 'polygon' | 'solana' | 'stellar' | 'tron' — The blockchain network on which the transaction occurred
      - `memo` string — An optional memo associated with the crypto transaction, if applicable
    - `related_transaction_ids` string[] — IDs of related card transactions
    - `stripe_issuing_transaction_id` string, nullable — The [Stripe Issuing transaction ID](https://docs.stripe.com/api/issuing/transactions/object?issuing_transaction_object-id), if the transaction is backed by Stripe Issuing

## Other responses

- `401` — Missing or invalid API key
- `500` — Unexpected error. User may try and send the request again.

---

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