# What does your reporting need from each payment?

[Choose a reporting strategy](https://devportal-simpay-sbx.winkpg.io/docs/decide/reporting-strategy.md): Whether to ask this platform for payment data on a schedule, or to have it sent to you as it happens, and what each one costs you to run.

Totals and individual payments come from different endpoints, so this is the fork that decides which half of the API you build against.

**Choose one**

- [A periodic total. Counts and amounts over a day, a week, or a month.](https://devportal-simpay-sbx.winkpg.io/docs/decide/reporting-strategy/how-current-the-totals-must-be.md): Nobody looks at an individual payment unless something is wrong.
- [Every payment on its own, with its own detail.](https://devportal-simpay-sbx.winkpg.io/docs/decide/reporting-strategy/how-soon-each-payment-is-needed.md): You show, store, or act on payments one at a time.

- [Start over](https://devportal-simpay-sbx.winkpg.io/docs/decide/reporting-strategy.md): go back to the first question.

## See also

- [All documentation](https://devportal-simpay-sbx.winkpg.io/llms.txt): the machine-readable index of every public page on this site.