#rovarma

1 messages · Page 1 of 1 (latest)

glass lodgeBOT
random creek
#

Or are they functionally identical, but just sent at different times?
that one

#

the status changes because it's when we thing the payout will have appeared in your bank account, but that's it. I'd use payout.created for reconciliation since that's when the list of transactions in the payout are locked

proud oak
#

alright, thanks!

#

related feature request then: it would be great if there was a webhook to notify of BalanceTransaction creation. Then we could do this in real time, rather than every X days whenever a payout happens 🙂

random creek
#

hmm, not sure what you mean. You know when a BT is created (for example its when an invoice.paid event is fired and you can expand invoice.payment_intent.charges.data[0].balance_transaction), they are created when a charge is captured basically.

#

then every day at around 1am we run a job to pull BTs for available funds into a payout and fire payout.created , so that's really the earliest you can know which payout a BT is going to appear in and then connect that to the related payment/invoice

proud oak
#

yes, but that doesn't include other BTs, like the ones created for Stripe fees (Billing, etc)

random creek
#

yes, those are just monthly adjustments we create

proud oak
#

exactly, so there is no hook currently to detect those. That's why I thought it would be nice of there was just a general 'BT.created' type event that fires for all these things, rather than having to handle invoice.paid, charge.succeeded, refund events, etc. But it's not a high priority, I can make do with the payout delay

random creek
#

I highly doubt we will ever add an event for creation of BTs since the volume would be way too high; our actual product answer here is intended to be to recommend the use of our Reporting APIs and such(https://stripe.com/docs/reports/payout-reconciliation), over using direct payout->BT approaches

proud oak
#

makes sense, thanks. I actually wasn't aware of the reporting APIs, but looking at it now it seems fairly limited in what it can do (and also having to parse CSV, etc), so we'll stick with this

#

anyway, I'll use payout.created then. thanks!