#devdoggingit_webhooks
gleaming palmBOT
👋 Welcome to your new thread!
⏲️ 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.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 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/1230531821825949908
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
vale rootBOT
dull frigate
Hi there 👋 sounds like you're using either Destination Charges, or Separate Charges & Transfers. With those, it can be tedious to trace from activities on the Connected Account to actions on your Platform account, because they're pretty separate with just the Transfer connecting them. The flow you're describing sounds like it's probably already the right one for getting the information needed.
Is your flow using Automatic Payouts, which is what lets you query the API for Balance Transactions that belong to a Payout?
hidden lily
Our flow's using automatic payouts yeah, exactly as you mentioned.
dull frigate
Gotcha, yeah, you've probably already found the best path then. If you were manually triggering Payouts, you could add metadata on them to make tracking things easier downstream, but that's not a small change to move to from automatic payouts.
Do you find yourself needing to do this for the same Payout repeatedly? If so you may be able to update the Payout and add metadata to it after doing the Transfer lookup once. You could store the ID of the related object in metadata so that you don't have to go hunting for it (and wait for API responses) if you've already found it before.
https://docs.stripe.com/api/payouts/update
hidden lily
Usually when we get the transfer we don't have to work backwards again because we update our DB records and we're good to go, it's just more the problem with it being caught in making repeated calls and slowing down our webhook, but I'm considering talking to the team about having it do these kind of 'reconciliation' events asynchronously as part of another task. I'll see if we can find a solution there.
Thank you! Just wanted to confirm that was our best option as it was, as you mentioned, becoming tedious, but I didn't see another option.