Skip to main content
GET
List card transactions

Overview

Returns a paginated list of card-level transactions sourced directly from the card network. This includes purchases, declines, refunds, reversals, and fees — everything that moved money on the physical card.
These are card-to-merchant transactions, not program ledger movements. For deposits, withdrawals, and card funding/unload events, use GET /transactions instead.

Path Parameters

Query Parameters

Transaction Object

References

references carries the identifiers a merchant, a cardholder’s bank or our support team needs to trace a card payment — for example when a cardholder asks a merchant for a refund. It is always present; funding and unloads carry no network identifiers, so for them it is an empty object. Each field appears only when the card network supplied it.
The ARN is assigned by the merchant’s acquirer when it submits the payment for clearing, so an authorization that has not cleared never has one. When arn is absent on a cleared payment, contact support with the rrn and authorizationCode and we will obtain it. A refund request to the merchant does not need the ARN — the merchant identifies the payment from its own order.

Example

Success Response (200)

If the card has not yet been fully provisioned by the card network, the data array will be empty and pagination.total will be 0.

Error Codes

Authorizations

Authorization
string
header
required

API key from the FYATU CaaS portal. Pass as Authorization: Bearer <key>.

Path Parameters

id
string
required

Query Parameters

page
integer
default:1

Page number (1-based)

Required range: x >= 1
limit
integer
default:20

Results per page

Required range: 1 <= x <= 100

Response

Card transactions retrieved

success
boolean
status
integer
message
string
data
object[]
pagination
object
meta
object