qmathe

[rocky totem]

there isn't really any clever solution beyond just paginating through the List PaymentIntent API

or you could export from the Dashboard into a CSV with some date filters and look through that file

what's the use case?

like export payments from the month when you remember you created your Stripe account

[arctic monolith]

I want to store Stripe payment data in my backend, so I'm using web hook events and working on solution to cope with potential lost events. For this last point, I list payment intents with starting_after set to the last payment intent id validated in my backend.

I was hoping to support deleting the entire payment data from my backend (during tests) and let my code resynchronizes everything. In this case, I'm missing a starting id.

[rocky totem]

makes sense. But yeah, as I said, there's no clever solution here, our List APIs always return in most-recently-created order, there's no way to change that

you just have to start from some point and continue paginating until has_more is false, and the last object in that array is the oldest object. It's just how the API is designed and the data is indexed.