#karls-paymentintent-list

1 messages · Page 1 of 1 (latest)

rancid spade
#

@storm viper do you have an example request id I can look at?

storm viper
#

Yes

#

req_rojMs3rrauCOAK

#

returns nothing...

#

req_HkC5uNpdC1VFUa

#

works (with no date specs)

rancid spade
#

looking

storm viper
#

thx

rancid spade
#

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?

storm viper
#

thinking..

#

on the Stripe dashboard, where do I see the latest payment intents?

rancid spade
#

there isn't really a place because you seem to sometimes use PIs and sometimes just direct Charge creation

storm viper
#

..and yes, that is the date I was expecting to pass, 11/9...

rancid spade
#

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

storm viper
#

I believe the majority of our transactions are direct charge..

#

I think everything is functioning correctly than. Thanks for clarifying!

rancid spade
#

sure thing! If you change gt to gte you'd get one result for example

storm viper
#

ah yes, but that specific date was the LAST item I fetched so actually using gt is correct implementation.

rancid spade
#

I'm dubious this is correct no. Are you trying to paginate? What if you had more than 100 payments at that exact second?

storm viper
#

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.

rancid spade
#

you're misunderstanding pagination

storm viper
#

*subtract couple of seconds from my LAST fetch

rancid spade
#

that means "give me the PIs before that specific PI I got in my last page"

storm viper
#

Also, I am using the auto pagination feature..

#

oh? looking.... however, if they both accomplish the same thing??

rancid spade
#

then just pass ending_before as the most recent id, there's no reason to use gt

storm viper
#

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

rancid spade
#

sure, then don't pass created at all. Pass ending_before: 'pi_123' which would be the most recent PI you got last

storm viper
#

OK... I think I was confused on which ID to send, or not certain of the results so early on I abandoned the ending_before approach. I may use it in the future.

#

Makes sense. Thank you.