#ed_webhooks

1 messages ยท Page 1 of 1 (latest)

teal copperBOT
#

๐Ÿ‘‹ 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/1354204246316159247

๐Ÿ“ 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.

  • ed_api, 5 days ago, 20 messages
  • ed_api, 6 days ago, 27 messages
bold pasture
#

But the most recent event claims that the account does not have payouts enabled

#

But if you look at acct_1QNeSzQY48e9yh0v, the account clearly has payouts enabled

#

Why are these webhooks this way???

#

It's really rough for us because as a system we expect that events can be sent out of order, but now we can't even tell what the right state of the account is. ๐Ÿ˜จ

daring garnet
#

Hi! The order of events is unpredictable, which is just the nature of asynchronous actions like this at large scale.

In this case, you'll want to retrieve the Account so you get the most up-to-date view of the object on which to act.

Create an event destination to receive events at an HTTPS webhook endpoint. Receiving webhook events is particularly useful for listening to asynchronous events such as when a customer's bank confirms a payment, a customer disputes a charge, a recurring payment succeeds, or when collecting subscription payments.

bold pasture
#

Hey @daring garnet can you help me confirm that the account should now have
charges_enabled & payouts_enabled both True?

#

I understand the network can cause delays, but even the event.created timestamp means nothing?

daring garnet
#

event.created should be pretty close to when it was created, but again, if you want to be sure you have the most current state when handling an event, just retrieve the object and you'll have its current state.

I can't confirm or refute that, no.

#

Further: event.created are to-the-second Unix timestamps, so many things could occur in the same second.

bold pasture
#

Yeah there should honestly be an atomic integer called snapshot.

daring garnet
#

That's one way to approach it, for sure - but that would only tell you what order to process them in, not whether you have the most up to date state.

teal copperBOT
bold pasture
#

@daring garnet do you know how I can fetch the current state of an account via the python api?

daring garnet
bold pasture
#

Btw, how long does stripe maintain their apis for? I think I'm on 2023 version - how long are those supported?

cosmic ledge
#

๐Ÿ‘‹ stepping in for my teammate. We don't have hard deprecation dates at the moment for any of our API versions at the moment

bold pasture
#

Sweet, that's great for us, but isn't that insane? Like isn't the oldest API version ancient haha?