#karls-paymentintent-list
1 messages · Page 1 of 1 (latest)
Yes
req_rojMs3rrauCOAK
returns nothing...
req_HkC5uNpdC1VFUa
works (with no date specs)
looking
thx
As far as I can tell the most recent PI in that second call was created at 1636483342. And you explicitly pass gt as this exact value, so it's expected you get no results since there's no PI after that exact timestamp?
there isn't really a place because you seem to sometimes use PIs and sometimes just direct Charge creation
..and yes, that is the date I was expecting to pass, 11/9...
but mostly, if you have a PI most recently created at time A and you say "give me all PIs created since A" then you get no result
I believe the majority of our transactions are direct charge..
I think everything is functioning correctly than. Thanks for clarifying!
sure thing! If you change gt to gte you'd get one result for example
ah yes, but that specific date was the LAST item I fetched so actually using gt is correct implementation.
I'm dubious this is correct no. Are you trying to paginate? What if you had more than 100 payments at that exact second?
I hear what you are saying.. I could always subtract a couple of second from my fetch and then reject the transactions I've previously fetched... I may implement that.
you're misunderstanding pagination
*subtract couple of seconds from my LAST fetch
https://stripe.com/docs/api/pagination you're supposed to use ending_before in that case
that means "give me the PIs before that specific PI I got in my last page"
Also, I am using the auto pagination feature..
oh? looking.... however, if they both accomplish the same thing??
then just pass ending_before as the most recent id, there's no reason to use gt
ok wait... the implementation:
Day1: I sync all payment intents
DayX: I sync all payments from last intent captured from Day1
DayXX: Repeat this syncing operation...
sure, then don't pass created at all. Pass ending_before: 'pi_123' which would be the most recent PI you got last