#mattcomroe_api
sinful laurelBOT
👋 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/1501207479302881442
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
sharp trail
hey there, taking a look at the examples you shared
stark atlas
hi! thanks so much for your help.
sharp trail
We've identified that the connected account ID fragment appears to be embedded in the
py_ID itself (chars 9–18), and we can use that to look up the correct account on our side — but this feels like undocumented behavior we'd be relying on.
You're correct about this -- that kind of embedded ID does exist, but it is not part of the API contract that you should build against. We might change that at any time without notice.
stark atlas
understood. undocumented and possibly brittle.. so that's why i was looking for the safest way to get from that capital.financing_transaction.created webhook event to the underlying source_transaction
stark atlas
the dashboard search is able to find it, but i'm sure it's doing something much more complex than an API call.
sharp trail
Still looking into this, and I think I've hit a dead end with an indication of transfer between those accounts (which look like they represent the ~same entity)
In particular, it appears to have been triggered when you made this OBO destination charge to the Jec6p account: https://dashboard.stripe.com/acct_19M5AiBnxMPxdETu/logs/req_XVqCC5hXhkmEip
As far as i can tell, there is no path to traverse this account transfer via the API as its handling an edge case with capital loans
I would suggest reaching out to your Stripe contact(s) for guidance on this, who will likely be working with the capital engineering team
The only way to capture this i can think of is tracking the received payments/transfers to your connected accounts and then looking that up there.
ie, subscribe to these payment.created events on your connect type endpoint and track the payment<>account link
https://dashboard.stripe.com/events/evt_1TTaIgPWhnQJec6pkrEsQHot
(this is the event for that account and payment)
stark atlas
hmm thank you for taking so much time out of your day to look at this. i believe the OBO we're setting is correct, so i will follow your advice and find our rep and see if we can get with the capital engineering folks on this.
Do you know if there's anything "useful" I can do with the legacy_balance_transaction_source handle in the FinancingTransactionCreated event? i.e. flxlnpd_1TTaJ1PfKJ4c8pMAGblfJtxT ?
sharp trail
It doesnt look like there's anything for that unfortunately. One option you can also explore is retrieving adjustment type balance transactions on the account, around the time of the transaction
https://docs.stripe.com/api/balance_transactions/list#balance_transaction_list-type
but even then I don't think you'll have visibility of the origin payment account