#yerayamenitiz_api
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฑ๏ธ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1212061690976407622
๐ Have more to share? You can add more detail below, including code, screenshots, videos, etc.
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question. Thank you for your patience!
Hi ๐ I don't know offhand if you can filter by Connected Account ID when filtering request logs in the dashboard, but by default we don't include requests made to your Connected Accounts in that view. You'll need to go into the filters and check the box for Outgoing Connect requests.
You can also uncheck the first two boxes there to remove logs from your Platform account from that view.
I'm seeing the dashboard as this connected account and when I go to the events and I choose the same filters as you (including the outgoing requests) I don't see any request for setup intent. Which should not be possible since I'm literally seeing the stripe elements being rendered in our customer's admin.
Oh, if you're viewing as the Connected Account, then everything I've said is wrong.
What type of charge flow are you using for Connect? Direct Charges or Destination Charges?
Where do I check that?
When you're creating your Payment Intents, do you set the transfer_data.destination parameter, or do you use the stripeAccount header?
transfer_data.destination
and we set the stripe connect accound ID of our customer there
Gotcha, so that's a Destination Charge flow. With that flow it's expected for you to not see a request to create a Payment Intent on your Connected Account, because the payment is completely happening on your Platform account and then a Transfer is created to move funds to the Connected Account.
You'd want to look at the logs for your Platform Account to see what is happening.
Okay so I should be able to see the payment intent request from my platform account logs, however, we have thousands of customers. Is there any way to filter them out based on this specific onnected account?
Can you try putting the ID of the Connected Account in the Filter by resource ID... field?
๐ฅฒ
it was that easy...
thanks for that
I'm sorry I have bothered you with such a simple thing
oh but wait, only payment intents are showing up
I don't see any setup intent
No worries! We all need a rubber duck sometimes.
Setup Intents don't accept a Connected Account ID as a parameter, so that seems expected.
You would likely need to search by a different value that was used to create those intents. You mentioned customers earlier, would you have a Customer ID to search with?
We create the SetupIntents with this params (customer, on_behalf_of and metadata)
Customer is not a reliable way since we are creating empty customers every time a setup is done.
OnBehalfOf is the Stripe connected account ID
and metadata contains very specific information for this request, which might be a realiable if there was a way to filter by metadata (I tried the search approach but SetupIntent won't accept it)
Do you already have the ID of a Setup Intent handy that you can share?
I do not have a setup intent ID for this connected account
I'd recommend continuing to play around with various resource IDs as filters then. I'm honestly not too familiar with the dashboard view, as my team spends most of our time in our SDKs and API.
Are you using on_behalf_of with your Payment Intents as well?
Yes, we do
Hm, I'm not sure if the dashboard logs index that field then, so you can search based on values provided to it.
I couldn't find any way besides going one by one, and we have thousands of requests
I don't think I'm spotting another way unless you have an associated object ID aside from the Connected Account ID.
Do you have a general ID of the issue you're looking for? If it's failing requests you can filter specifically for failed ones. But if the requests are successful, but the desired outcome still isn't being achieved, that's going to be harder to track down.