#devops_webhooks

1 messages · Page 1 of 1 (latest)

dark rockBOT
#

👋 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/1413163471599829002

📝 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.

hidden remnant
#

Hi, as my teammate notes, there is account.updated, evt_1RksYlRh6F4BcJAO0sFPuJTO event that did show all eventually_due requirements.

#

What are you exactly looking for that is not on there?

lyric cobalt
#

I'm looking for an event that gets emitted when the connected account is moved to the restricted state

dark rockBOT
hidden remnant
lyric cobalt
#
  1. Thats not what I'm looking for, so to confirm there isn't an event that gets emitted when an account is moved to restricted, correct?
  2. Looking at evt_1RksZhRh6F4BcJAOYBwNQtBE, deadline is null:
"requirements": {
                            "alternatives": [],
                            "current_deadline": null,
                            "currently_due": [],
                            "disabled_reason": null,
                            "errors": [],
                            "eventually_due": [
                                "person_1RksRLRh6F4BcJAOtYW1kJbz.id_number"
                            ],
                            "past_due": [],
                            "pending_verification": []
                        },
#

I'll be commuting, i'll be back online in ~30 minutes

lyric cobalt
#

back -- confirming ^ ?

latent jacinth
#

Hi there, taking over for @hidden remnant as they needed to step away

#

The account.updated event will occur when anything in the requirements changes or if the account capabilities are updated. It sounds like this is what you need to proceed?

lyric cobalt
#

Please let me know what event corresponds to the account moving to restricted between August 29th and September 3rd

#

I cannot find such an event, but at some point during this period, the account was updated so that payouts stopped

latent jacinth
#

Got it. Can you let me know which account was moved to restricted and what you see that indicates that it is restricted?

lyric cobalt
#

acct_1Rkro4Rh6F4BcJAO - looking at the payout history, you can see on sep 3 payout didn't happen at the correct time

#

In the UI, we saw a pop up similar to this when looking at the account

image.png
latent jacinth
#

Got it. Nothing looks restricted on our end, so you'll need to reach out to support https://support.stripe.com/ for guidance on requirements highlighted on the dashboard and the details for the payouts on that account.

Stripe: Help & Support

Find help and support for Stripe. Our support site 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.

lyric cobalt
#

Nothing is currently restricted. We already fixed the issue.

#

Can you confirm there is no event emitted when an account is restricted due to an eventual requirement?

fading swallow
#

Hey there just hopping in as nobs had to head to a meeting.

We see no indication this was restricted. If the account capabilities became inactive or charges/payouts were disabled, there should be an account.updated event.

I would suggest working with support to understand what was surfaced to you in Dashboard (we can't really speak to that part) and the payouts you observe.

lyric cobalt
#

Can you confirm there is no event emitted when an account is restricted due to an eventual requirement?

#

I can reach out to support (we already did yesterday to get this resolved), but purely technical question about what event gets emitted when this happens (if any)

fading swallow
#

eventual requirements should not modify account capabilities -- they would need to move to currently/past due first
https://docs.stripe.com/connect/handling-api-verification#determine-if-verification-is-needed

eventually_due: Requirements that you might need to collect, depending on whether the corresponding thresholds are reached. After a requirement becomes required, it also appears in the currently_due list. If a requirement becomes required and its due date is before the existing current_deadline, the current_deadline changes to the corresponding threshold’s enforcement date.

#

If an eventually_due requirement became required, there would be an account updated event to update currently_due etc

#

If any missed requirement impacted an account capability, an account.update event would be emitted to reflect that capability change

#

An account should not have a capability inactivated or charges/payouts disabled without a corresponding account.updated event

lyric cobalt
#

I see, that makes sense. If support comes back and corroborates our account of the issue (the account was updated such that payouts don't work), what are the next steps? Because it doesn't seem like there are any events for that happening, right?

dark rockBOT
snow notch
#

👋 stepping in as synthrider needs to step away.

#

If a property changed on the Account object without an account.updated Event firing then that would be a bug we would need to look into. You could share those specifics with the Support team and they can coordinate with the Engineering team on that. But right now we don't see anything that indicates there was a change here.

lyric cobalt
#

Great, thank you. One final question -- for evt_1RksZhRh6F4BcJAOYBwNQtBE, why is deadline null even though there was something eventually due?

"requirements": {
                            "alternatives": [],
                            "current_deadline": null,
                            "currently_due": [],
                            "disabled_reason": null,
                            "errors": [],
                            "eventually_due": [
                                "person_1RksRLRh6F4BcJAOtYW1kJbz.id_number"
                            ],
                            "past_due": [],
                            "pending_verification": []
                        },
snow notch
#

Are you sure that is the correct Event? It is deleted at this point (past 30 days) so I can't see the payload. Or did you just store the Event on your side?

lyric cobalt
#

we store the events

#

i can send you the whole event if that helps?

snow notch
#

I believe the reason for it being null is that some requirements are threshold based, like a monetary volume amount on the account. Thus there can't be a specific deadline until that threshold is passed.

lyric cobalt
#

Ah okay got it, thats all for now then. Thank you!