#oliver_webhooks
1 messages ¡ Page 1 of 1 (latest)
đ 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/1407825642866868471
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Apoligies, I meant after payments have been processed. Thank you.,
Hello, my memory on the specifics are a bit fuzzy but I do know this is possible/expected to happen on occasion with async payments like ACH. Do you have any specific questions around how this works? I can make sure to keep an eye out while refreshing my memory
Thanks Pompey. This has also happened with credit cards. I can try and find a specific case in which this happened.
My question is: what is the best approach toward reconciling payouts with successful payments given the async nature of the events? Once we get a payout.paid event, is there a recommended workflow?
Good question. Do you have some existing process in place that tries to reconcile this that async payments are messing with? Or is this a question on building something to reconcile that connection in general?
we have an existing process in which we show our users a list of all their payouts that have been paid out, and the corresponding payments received via stripe connect
when we receive the payout.paid event, we check the Stripe Balance Transactions to fetch the successful charges associated with it and link them together internally
I suggested to our team we could trigger payouts manually instead
Ah gotcha, and the async payments aren't included in the balance transaction list?
I wonder if with automated payouts there is a suggestion
not until those payments are confirmed
Yeesh, that is a fun edge case if I've ever heard one
Thanks for the clarification, looking in to if there is a suggested workaround with my colleagues
thank you!
One of the complications here is that we don't have this same mapping of balance transactions to payouts for manual payouts, so that would be something you would have to start keeping track of if you switched to manual.
yeah, but since we can initiate payouts with specific amounts, it would be easier for us to map the payments to them one-to-one, for example
It would just require an important change in our current setup that I'd rather avoid if possible
While I am looking can you send over any example payments you know of where this happened for a card payment? The succeeded events for them should happen days before their balance is available so I am surprised to hear this can happen for them
sure, let me try to find one
my bad Pompey, I thought I had noticed situations like that with card payments. You are correct in that it only happens with some ACH payments.
I have to sign off as it is a bit late for me, but I will make sure to check back tomorrow. Thank you so much for your help! I really appreciate it.
Sounds good, unfortunately I'm not finding much on this. I think there may be marginal improvements, like checking to see if the sum of the balance transactions lines up with the payout amount and making the breakdown available immediately if so. But I don't think there is a good workaround to just get this case to work at the moment.
Another thing that I am thinking is that because this should be a pretty rare occurrence, you may be able to reconcile the remaining amount by using the Search API to find payment intent(s) for the account that are still in a processing state and see if the amount on their balance transaction lines up with the missing amount on the payout.