#mibrahim15

1 messages · Page 1 of 1 (latest)

hazy knotBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

real rapids
#

What do you mean charges "like this"

storm leaf
#

starting with py_

#

py_3NZjR24V4UG4b3Qn0dvF0VAY

This is being fetched when Retrieving single charge, as well as when listing Payment Intents but not when listing Charges

#

@real rapids you around?

real rapids
#

We help many users in here

#

Please be patient

storm leaf
#

sure

real rapids
#

Ok looking

#

The py_ id shows when listing payment intents?

storm leaf
#

Thanks in advance

real rapids
#

Or its pi_ shows when listing payment intents?

storm leaf
#

py_ shows inside pi_ object , as paymentintent have charges object inside it so i am talking aboout that

real rapids
#

Well yeah

storm leaf
#

not shown directly

real rapids
#

That's expected

#

Let me ask a colleague if py_ id's associated with payment intents not showing up in the charge list call is expected though

#

But first, do you have the request id of the list Charges call that didn't include this py_ id?

#

Want to just make sure the call was formulated properly

storm leaf
#

Yes I can proviide you shortly, asking to my colleague, he have access to dashboard

hazy knotBOT
storm leaf
#

Hey, @real rapids its
req_SWKVXj6v60CfSz

AND

req_m9d9LU4QQvaJMk

#

Request body
{
"limit": "200",
"starting_after": "ch_3NY8fI4V4UG4b3Qn0zo9CNjz",
"created": {
"lte": "1690415999",
"gte": "1690329600"
},
"expand": {
"0": "data.balance_transaction"
}

#

@regal mortar

regal mortar
#

HI 👋

Thanks for the request IDs, let me take a look

storm leaf
#

Thanks in advance

regal mortar
#

Okay for the first request, the created parameters would exclude the py_ you shared earlier

#

You are passing a time window from 7/25 - 7/26 but that charge was created on 7/30

#

That is true for both requests

storm leaf
#

I mean

#

whenever I send a request I dont get any Charge with py_

#

for any date range

regal mortar
#

Can you share a request with a wider date range?

storm leaf
#

there are other IDs with py_ as well on dashboard will fall in the date range from 7/25 - 7/26 but not included

regal mortar
#

there are other IDs with py_ as well on dashboard will fall in the date range from 7/25 - 7/26 but not included
THose would be the useful ones to share, since we would actually expect them to show up in these API requests

storm leaf
#

py_3NYFnW4V4UG4b3Qn086fLM1q
py_3NYFjB4V4UG4b3Qn0tqlsQCV

req_2Dimb5tG6EJ11k
req_U9AOn4e3hkOx2u

{
"limit": "200",
"starting_after": "ch_3NXwec4V4UG4b3Qn1oPhN3M5",
"created": {
"lte": "1690415999",
"gte": "1690329600"
},
"expand": {
"0": "data.balance_transaction"
}

{
"limit": "200",
"starting_after": "ch_3NXvUz4V4UG4b3Qn0EXzcTAz",
"created": {
"lte": "1690415999",
"gte": "1690329600"
},
"expand": {
"0": "data.balance_transaction"
}
}

#

Can you chec these IDS

#

I will try auto pagination as well, I actually have this thing already implemented.. So I would love some quick solution if there is any..

regal mortar
#

I don't have a "quick solution" for you here. I think it would be faster to write a quick script that auto paginates through all your charges and prints out a log message when you find the matching IDs

#

Your search parameters are still too narrow

#

Also the maximum limit is 100 objects so passing limit: 200 is pointless