Query the transactions list
Ask for the payments you want, when you want them, with the filters on the list endpoint.
Your answers so far
Choose one
What to build
Call the transactions list with the filters that describe your window, and page through the result. Run it on a schedule for a periodic load, or on demand when somebody opens a report. At this volume there is nothing a webhook receiver would buy you that a filtered request doesn't already give you, without an endpoint to deploy, secure, and keep available.
What this means for PCI
This is guidance rather than a compliance determination. Which questionnaire you are eligible for depends on your full environment, so confirm it with your QSA or your acquirer before you rely on it.
Worth knowing
- Filter on a closed window and page to the end of it. Paging is by continuation token, so follow the token rather than asking for a page number.
- A payment's state moves after it's created. Decide whether your load is reading new payments or re-reading recent ones for their current state, because a window that only looks at creation time never sees the second.
- Polling counts against your rate allowance like any other call. A tight loop over a quiet window spends it on responses that repeat the last one.