#alex.tomuta-balance-events
1 messages · Page 1 of 1 (latest)
hi ynnoj, sure
this is the pending one evt_1KlO37RhOo5I9UvAjjeVzJLV
but there's no subsequent available one
Sorry, still checking on this
Confirming that this is expected behaviour
What are you trying to do?
This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
in general balance.available events are not really supposed to be for granular transaction-by-transaction notification.
The integration pattern is that every day, you should get a balance.available event . At that point, you need to check which charges have been released. The best solution is to look into your database for each charge supposed to be released that day (the available_on field on a BalanceTransaction) and then retrieve the corresponding balance transaction via the API to confirm the status property to confirm that the funds have been made available.
What are you really trying to do?
we have a platform integrating merchants and vendors - each vendor has connected account as well. For some vendors, the payout needs to be done in a non-usd currency
also, one thing to mention that's an edge case
so we're waiting for the balance.available event to trigger the payout
you don't get a balance.available if funds move from pending to available but your overall balance remains negative
because as we saw, in some cases, the conversion phase might take up to 24 h
makes sense!
ah I see, so it's not really the ideal solution for our use-case