Customer transactions
Customers
List Customer Transactions
Retrieve all card-related transactions for a single customer across every card they hold.
GET
Customer transactions
Overview
GET /customers/{id}/transactions returns the union of card transactions across every card owned by the specified customer — fundings, withdrawals, merchant authorizations, settlements, refunds, and cross-border charges. The response is paginated.
To filter to a single card, use GET /cards/{id}/transactions instead.
When to use it
- Render a customer’s full activity timeline.
- Compute a customer’s total spend across all their cards.
- Audit a customer for unusual activity.
Prerequisites
- The customer must belong to your company.
Request
Headers
| Name | Required | Description |
|---|---|---|
Authorization | Yes | Bearer <access_token> |
Path parameters
| Name | Type | Description |
|---|---|---|
id | string | Customer ID (UUID). |
Query parameters
| Name | Type | Default | Description |
|---|---|---|---|
page | integer | 1 | 1-indexed page number. |
limit | integer | 10 | Items per page (max ~100). |
Response
200 — Success
GET /cards/{id}/transactions — see that page for a full field reference. The only difference is the customer block is not included (you already know which customer you queried).
Error responses
| Status | Trigger |
|---|---|
404 | Customer does not exist or belongs to another company. |
Code examples
cURL
Related
GET /cards/{id}/transactions— same data filtered to a single card.- Webhooks → Transaction events — receive new transactions in real time.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.