#leona7244

1 messages · Page 1 of 1 (latest)

dawn acornBOT
#

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.

subtle coral
#

I think this might be a syntax issue? Are you then printing the results of that stripe.paymentIntents.list call?

vernal crater
#

yes i tried to log it in the terminal

#

everything was fine when i didn't make the call with connect account

subtle coral
#

Can you try hard coding the value of stripeAccount instead just for testing purposes?

vernal crater
#

you mean from the request?

#

i can totally log it out

subtle coral
#

If you're saying this code worked just fine before it was updated to make the request as a connected account, I want to rule out any variables

#

Do you have an example PaymentIntent ID? I'd like to use this to pull up request logs on my end

vernal crater
#

yes i'll just copy one of the payment id from one of the connected account dashboard

#

py_1Oa2gOQeQb2dSpmllGK8OGOx

subtle coral
#

Thanks! Okay, the results you're seeing are expected. The PaymentIntents in this case are being created on the platform account, not the connected account. So retrieving PaymentIntents as the connected account will not return any results

vernal crater
#

ohhh yes, you're right it was created on our platform account, but we do want something like a report for connected accounts, is there a way of doing it

subtle coral
#

You'd make this call as the platform since you want to pull all transfers made from the platform to that specific destination