> ## Documentation Index
> Fetch the complete documentation index at: https://kb.paymentsmojo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Card transactions

> Every captured sale and refund on your MIDs, however it was made, and the deposit that paid it out.

Card transactions are every sale captured, and every refund made, on your MIDs: one list, whatever made them.

| `source` | Where it came from |
| - | - |
| `Invoice` | An invoice paid on your payment page, or taken on a card terminal |
| `Recurring` | A recurring plan's approved charge |
| `PosGateway` | A sale or refund from your point of sale through the [POS Gateway](https://kb.paymentsmojo.com/api/overview.md) |
| `Processor` | A card payment made outside Mojo Payments, such as on the processor's own virtual terminal |

Mojo Payments' own payments appear within a minute of being captured. Payments made outside Mojo Payments appear when
the processor pays them out, usually one to two business days after the sale. An authorization that's never captured
isn't a card transaction: no money moved.

Needs: an API key with `payments.view`.

## List them

`GET /card-transactions` lists them, newest first, a page at a time ([Pagination](https://kb.paymentsmojo.com/developers/pagination.md)); sort by
`date`, `amount`, `mid` or `funded`. Filter with:

| Parameter | Keeps |
| - | - |
| `from`, `to` | Captured between these dates (`2026-10-01`), inclusive |
| `mid` | One MID |
| `source` | `Invoice`, `Recurring`, `PosGateway` or `Processor` |
| `kind` | `Sale` or `Refund` |
| `status` | `Captured` (not paid out yet), `Voided` or `Funded` (paid out in a deposit) |

Each has its `retRef` (the processor's reference), `kind`, `source`, `status`, `amount` (tip included; never negative:
a refund's `kind` says so), `tipAmount`, card brand and last four when known, `orderId` (the invoice number, the plan's
reference or the POS's order id), `customerName`, when it was captured, and when it was voided or paid out, with the
`depositId`.

```bash theme={null}
curl "https://api.paymentsmojo.com/card-transactions?status=Funded&from=2026-10-01&to=2026-10-31" \
  -H "Authorization: Bearer eyJ…"
```

## One transaction

`GET /card-transactions/{id}` adds what it was in Mojo Payments: the `invoiceId`, `recurringPlanId` or
`posGatewayTransactionId`, so you can read the invoice's lines, the plan, or the POS call. Read the deposit that paid it
out with `GET /deposits/{depositId}` ([Deposits](https://kb.paymentsmojo.com/developers/deposits.md)).

## Be told as they happen

The [webhook](https://kb.paymentsmojo.com/developers/webhooks.md) scopes `cardTransaction/created` (a new sale or refund) and
`cardTransaction/updated` (voided, or paid out in a deposit) name the transaction; read it with
`GET /card-transactions/{id}`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.