Skip to main content
Card transactions are every sale captured, and every refund made, on your MIDs: one list, whatever made them. 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); sort by date, amount, mid or funded. Filter with: 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.

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

Be told as they happen

The webhook 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}.