#kem-connect-header
1 messages · Page 1 of 1 (latest)
kem-connect-header
@tidal sundial that account is an Express account. That means you should be using Destination Charges https://stripe.com/docs/connect/destination-charges and all the PaymentIntents live on your own platform. I confirmed it is what you do. So there's no reason to make that call on the connected account. All the PaymentIntents live on your platform
so i want to get payment intents for spefic account hot to do it in stripe in nodejs?
So to reword your question, you have PaymentIntents, each with their own "destination account" using transfer_data and you want to filter the ones that went to a specific connected account?
That isn't possible, we don't have such a filter today on the List PaymentIntents API.
What you can do instead is use the List Transfers API https://stripe.com/docs/api/transfers/list which has a destination filter: https://stripe.com/docs/api/transfers/list#list_transfers-destination
This gives you all the Transfers from your platform to a given connected account. Those Transfers are "linked" to the original Charge and PaymentIntent in your account which you can expand back.
Look at the diagram here: https://stripe.com/docs/connect/destination-charges#flow-of-funds-amount to understand how those objects are connected to each other.
And then also look at the docs for our Expand feature https://stripe.com/docs/expand to access all the information you need
So who in stripe shell can do the funticationalty that i wnat and in the code i dont ??!!
I don't know, I never use Stripe shell, it's a UI tool and I don't really know what happened there but you can ask our support team for help: https://support.stripe.com/contact
ok thanks u
I did just try and have the same bug lol
if I pass --stripe-account acct_LOL it works instead of saying "acct_LOL does not exist" I'll report the bug
@tidal sundial you can close this issue, there's no reason to file this on stripe-node at all since I explained the logic and that there's no API bug