# Card Transactions

> Coming soon, upon request — this feature is turned on for your tenant by the Aurea team. [Contact us](https://www.aureahub.com/contact)

The payments made with the user's cards, as the card program records them.

## Overview

- Every filter is optional and passed on as sent: `before` and `after` (dates), `currency`, `mcc` (the merchant category code) and `type`.
- The answer is the card program's, as it came: a list, or the list under `transactions`. Each transaction's fields are the card program's — among them `id`, `amount`, `currency`, `billingAmount`, `billingCurrency`, `merchantName`, `merchantMcc`, `type` (`payment`, `refund` or `reversal`), `date` and `onChainStatus`.
- Inside the card program session (`403` `CARD_PROGRAM_SESSION_EXPIRED`).
- **Illustrative example.** The card program's answer is passed through unchanged and may carry fields not listed here: the example shows only the fields Aurea or its own app reads. Ignore the fields you do not know.

## Endpoint

### `GET /v1/cards/transactions`

Authentication: bearer token required.

The user's card transactions.

**Query parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `before` | string | no | Only transactions before this date |
| `after` | string | no | Only transactions after this date |
| `currency` | string | no | A currency code |
| `mcc` | string | no | A merchant category code |
| `type` | string | no | A transaction type of the card program |

**Responses**

`200` OK (illustrative)

```json
[
  {
    "id": "8d2e…",
    "amount": 3.5,
    "currency": "EUR",
    "billingAmount": 3.5,
    "billingCurrency": "EUR",
    "merchantName": "Caffè Roma",
    "merchantMcc": "5814",
    "type": "payment",
    "date": "2026-10-12T18:41:07.000Z",
    "onChainStatus": "…"
  }
]
```

**Example request**

```bash
curl "https://api.aureahub.com/v1/cards/transactions?after=2026-10-01" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
```

---

Web version: https://docs.aureahub.com/#cards-transactions