# Where do these payments end up on your side?

[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.

A stream you act on and a store you have to keep complete are different obligations, and only the second one needs a way to notice a gap.

**Your answers so far**

- What does your reporting need from each payment? Every payment on its own, with its own detail.
- How soon after a payment do you need it? Within seconds of the payment.

**Choose one**

- [In a reporting system of ours that has to hold every payment.](https://devportal-simpay-sbx.winkpg.io/docs/decide/reporting-strategy/webhooks-with-a-backfill-sweep.md): A warehouse, a ledger, or anything you reconcile against.
- [Nowhere lasting. We act on each payment and move on.](https://devportal-simpay-sbx.winkpg.io/docs/decide/reporting-strategy/subscribe-to-webhooks.md): A confirmation email, a fulfilment job, or a notification.

- [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.