#omkar_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/1303559607498571836
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- omkar_transfer-balance, 1 day ago, 132 messages
evt_3QHu4YGa8Tfgfn4e1zDjdEHj is the account balance of the platform account, not connected account.
account will only be available if the event is for a connected account.
But getting "Card Payments" not enabled error which is a different issue.
Was this error thrown from your CLI command?
Yes this was thrown from my CLI command
stripe trigger balance.available --stripe-account acct_1OSsLlGanIaJxuuT
Maybe because the simulation is charging the account by card and not by bank account?
@viral wasp
Here is what I am looking for help with, we have webhook code in Production but none of our connected accounts have fired the balance.available event since funds are still settling.
I am looking to test our integration early but am unable to successfully getting the AccountID from the eveny
Could you share an example live connected account (acct_xxx), so that I can take a look?
acct_1OSsLlGanIaJxuuT this is live
acct_1OSstUGg3wUaV08R <--- this is another example with more recent transfers
The balance.available event only triggers whenever the Stripe balance has been updated (e.g., when a charge is available to be paid out) [0].
Looking at the earliest charge on acct_1OSsLlGanIaJxuuT (py_1QH1U6GanIaJxuuTdS7CHVHV), the funds only become available on 13/11 (txn_1QH1U6GanIaJxuuT4OQaSKwv).
This is why there isn't any balance.available event triggered yet.
[0] https://docs.stripe.com/api/events/types#event_types-balance.available
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
This is the same for acct_1OSstUGg3wUaV08R as well. The earliest charge (py_1QHoGRGg3wUaV08RqBqEmnRo), only becomes available on 14/11 (txn_1QHoGSGg3wUaV08RiEtmpnJs).
Do note that the platform account (acct_1MyRVfGa8Tfgfn4e) currently only has an account webhook endpoint but no connect webhook.
While I understand that, is there a way for me to test this early ?
I cannot wait that long to test only to find out it doesnt work
You can test this by using these test cards: https://docs.stripe.com/testing#available-balance