> ## 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.

# List card transactions

> Every captured sale and refund on the merchant's MIDs, a page at a time, however it was made: an invoice (`Invoice`), a recurring charge (`Recurring`), a register through the POS Gateway (`PosGateway`), or outside Mojo (`Processor`, which arrive when the processor pays them out). Filter by `from` and `to` (capture dates), `mid`, `source`, `kind` (`Sale` or `Refund`) and `status` (`Captured`, `Voided`, `Funded`). Authorizations that were never captured aren't card transactions. Amounts are in dollars, never negative; a refund's kind says so.



## OpenAPI

````yaml /api-reference/openapi.json get /card-transactions
openapi: 3.1.1
info:
  title: Mojo Payments API
  description: >-
    Invoices, deposits, payments and locations for merchants; the merchant
    portfolio for reseller partners. Authenticate with an API key: exchange it
    at `POST /oauth/token` for a 10-minute access token, and send that as
    `Authorization: Bearer <token>`. Guides:
    https://kb.paymentsmojo.com/developers/overview
  version: '1'
servers:
  - url: https://api.paymentsmojo.com
security:
  - Bearer: []
tags:
  - name: Locations
  - name: Reseller portfolio
  - name: Invoice payments
  - name: Customers
  - name: Campaign pages
  - name: Authentication
  - name: Merchant accounts (MIDs)
  - name: Merchant applications
  - name: POS Gateway
  - name: Deposits
  - name: Card transactions
  - name: Recurring billing
  - name: Webhooks
paths:
  /card-transactions:
    get:
      tags:
        - Card transactions
      summary: List card transactions
      description: >-
        Every captured sale and refund on the merchant's MIDs, a page at a time,
        however it was made: an invoice (`Invoice`), a recurring charge
        (`Recurring`), a register through the POS Gateway (`PosGateway`), or
        outside Mojo (`Processor`, which arrive when the processor pays them
        out). Filter by `from` and `to` (capture dates), `mid`, `source`, `kind`
        (`Sale` or `Refund`) and `status` (`Captured`, `Voided`, `Funded`).
        Authorizations that were never captured aren't card transactions.
        Amounts are in dollars, never negative; a refund's kind says so.
      parameters:
        - name: from
          in: query
          schema:
            type: string
            format: date
        - name: to
          in: query
          schema:
            type: string
            format: date
        - name: mid
          in: query
          schema:
            type: string
        - name: source
          in: query
          schema:
            type: string
        - name: kind
          in: query
          schema:
            type: string
        - name: status
          in: query
          schema:
            type: string
        - name: page
          in: query
          description: The page, from 1. Default 1.
          schema:
            minimum: 1
            type: integer
            format: int32
        - name: pageSize
          in: query
          description: Items per page, up to 100. Default 25.
          schema:
            maximum: 100
            minimum: 1
            type: integer
            format: int32
        - name: sort
          in: query
          description: What to sort by. Default date.
          schema:
            enum:
              - date
              - amount
              - mid
              - funded
            type: string
        - name: dir
          in: query
          description: Sort direction. Default desc for date, asc otherwise.
          schema:
            enum:
              - asc
              - desc
            type: string
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PagedOfCardTransactionView'
        '401':
          description: >-
            No access token, or it expired or its key was revoked. Get a new
            token.
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemDetails'
        '403':
          description: >-
            The key doesn't have the permission this needs, or the organization
            is suspended.
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemDetails'
        '429':
          description: Too many requests. Wait and try again.
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ProblemDetails'
components:
  schemas:
    PagedOfCardTransactionView:
      required:
        - items
        - page
        - pageSize
        - total
        - sort
        - dir
      type: object
      properties:
        items:
          type: array
          items:
            $ref: '#/components/schemas/CardTransactionView'
        page:
          pattern: ^-?(?:0|[1-9]\d*)$
          type:
            - integer
            - string
          format: int32
        pageSize:
          pattern: ^-?(?:0|[1-9]\d*)$
          type:
            - integer
            - string
          format: int32
        total:
          pattern: ^-?(?:0|[1-9]\d*)$
          type:
            - integer
            - string
          format: int32
        sort:
          type: string
        dir:
          type: string
    ProblemDetails:
      type: object
      properties:
        type:
          type: string
        title:
          type: string
          description: A short summary, e.g. "Check the request".
        status:
          type: integer
          format: int32
        detail:
          type: string
          description: What to change, in plain words.
        errors:
          type: object
          additionalProperties:
            type: array
            items:
              type: string
          description: Field validation messages, by field (400 only).
      description: What went wrong (RFC 9457).
    CardTransactionView:
      required:
        - id
        - mid
        - locationName
        - retRef
        - kind
        - source
        - status
        - amount
        - tipAmount
        - cardBrand
        - lastFour
        - authCode
        - orderId
        - customerName
        - capturedAt
        - voidedAt
        - fundedOn
        - depositId
      type: object
      properties:
        id:
          pattern: ^-?(?:0|[1-9]\d*)$
          type:
            - integer
            - string
          format: int64
        mid:
          type: string
        locationName:
          type:
            - 'null'
            - string
        retRef:
          type: string
        kind:
          type: string
        source:
          type: string
        status:
          type: string
        amount:
          pattern: ^-?(?:0|[1-9]\d*)(?:\.\d+)?$
          type:
            - number
            - string
          format: double
        tipAmount:
          pattern: ^-?(?:0|[1-9]\d*)(?:\.\d+)?$
          type:
            - 'null'
            - number
            - string
          format: double
        cardBrand:
          type:
            - 'null'
            - string
        lastFour:
          type:
            - 'null'
            - string
        authCode:
          type:
            - 'null'
            - string
        orderId:
          type:
            - 'null'
            - string
        customerName:
          type:
            - 'null'
            - string
        capturedAt:
          type: string
          format: date-time
        voidedAt:
          type:
            - 'null'
            - string
          format: date-time
        fundedOn:
          type:
            - 'null'
            - string
          format: date-time
        depositId:
          pattern: ^-?(?:0|[1-9]\d*)$
          type:
            - 'null'
            - integer
            - string
          format: int64
  securitySchemes:
    Bearer:
      type: http
      description: >-
        An access token from POST /oauth/token (your API key's id and secret).
        It lasts 10 minutes.
      scheme: bearer
      bearerFormat: JWT

````

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