## TL;DR

Use the list-transactions endpoint with a customer filter: GET https://api.paystack.co/transaction with the customer query parameter set to the customer ID. Get the customer ID first from the customer endpoint, then pass it as the filter.

## Steps

1. Use the list-transactions endpoint with a customer filter: GET https://api.paystack.co/transaction with the customer query parameter set to the customer ID. Get the customer ID first from the customer endpoint, then pass it as the filter. The customer object itself will not carry the transaction list, so filtering the transaction list is the supported path for per-customer history.

## When to use

You are seeing this: The customer object itself will not carry the transaction list, so filtering the transaction list is the supported path for per-customer history. Use this skill when you run into "List a Paystack customer's transactions via the transaction endpoint filtered by customer".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- https://api.paystack.co/transaction
