#avery_account-history

1 messages · Page 1 of 1 (latest)

brave ravenBOT
#

👋 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. Thank you for your patience!

⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.

🔗 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/1212904570070769684

📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.

muted locustBOT
#

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.

jolly kayak
#

avery_account-history

sturdy walrus
#

Sup Koopajah

#

Sorry it's me again

jolly kayak
#

Hello! Totally fine to ask multiple questions, we're here to help 🙂

#

@sturdy walrus In the API it's not possible to "see" the history of an Account over time unfortunately.
There are 2 possibilities though

  1. The account.updated Event which would show each "change" to an Account and have previous_attributes (what was before) to diff. Those are only available for 30 days but can be helpful to debug things
  2. Request logs: in the Dashboard you can see API Requests that happened on a given account such as when you/they change their address, add their SSN (though you can't see the value), etc. Those are kept for a year (though no guarantees it'll always be there) and can be useful to debug what changed
sturdy walrus
#

Does the account.updated contain updates from when Stripe changed their account status

#

Basically what I am trying to find is when was an account notified of possible restrictions, when was it restricted, and when was it reinstated

#

Just got like 5 accounts disabled and confused since the new verification was supposed to be on March 15th or something

jolly kayak
#

yes all of that would be in the Event(s)

#

if you have one example account id I can show you

sturdy walrus
#

Yeah that'd be awesome

#

acct_1O9WvVPCk5hg7OiZ

#

I am seeing some

#

Does the event contain the entire body or just the changes?

#

Wait evt_1OoU9MPCk5hg7OiZGV6m1ze0

jolly kayak
sturdy walrus
#

Yeah I see that

#

For the event I sent

#

I see the changes at the bottom basically?

jolly kayak
#

ah wait are you not listening to account.updated on your WebhookEndpoint as a platform? If not that's a pain to debug

sturdy walrus
#

I think I see what it's saying though

jolly kayak
#

Yeah as a platform you really ought to have a Connect WebhookEndpoint that listens to account.updated Events from all your connected accounts to monitor things.

sturdy walrus
#

The event I sent basically shows that there was no requirements, then they added pending and requirements the same day

jolly kayak
#

yeah which is possible

#

and no that's not what the Event means

sturdy walrus
#

Oof I am lost

jolly kayak
#

That Event has previous_attributes: { payouts_enabled: true }
that means that before the Event they had payouts_enabled: true and their Payouts worked and after the Event their Payouts are disabled and they have payouts_enabled: false
nothing else changed in that Event. The requirements were there before that Event

sturdy walrus
#

Wait I think I sent the wrong one

jolly kayak
#

possible, requirements can trigger a lot of different Events. Important to take them carefully one by one and read them calmly

sturdy walrus
#

Wait no I think it's right no?

#

future_verification was empty now it's filled

jolly kayak
#

lol that's a really confusing sentence "no yes no"

#

what talestells you it was empty before?

sturdy walrus
#

First image is the previous

#

Second image is the object

jolly kayak
#

that previous_attributes is not in the Event you shared with me. Are you looking at another one?

Also that first picture tells you that pending_verification changed. It doesn't tell you that nothing was in future_verification before so you are definitely misunderstanding things

sturdy walrus
#

acct_1O9WvVPCk5hg7OiZ/events/evt_1OoU9MPCk5hg7OiZGV6m1ze0

#

Is the url I am on

#

I guess the question is, does the object in the event show the most updated version of the object

#

And does the previous attribute show what the object was before

jolly kayak
#

When you look at an account.updated Event, the object has the exact version of the Account at the time of Event creation and previous_attributes has the list of properties that changed.

sturdy walrus
#

Okay

#

So looking at the event I sent, there was no required verification before the event, then the event added that verification

jolly kayak
#

what does that mean "there was not required verification before"?

sturdy walrus
#

verification object is empty

#

I'm just trying to see if this is the event that locked this account lol

#

and seeing if they had a warning before hand or the account was locked instantly

jolly kayak
#

verification hash has been deprecated for over 5 years now which also doesn't help

sturdy walrus
#

we don't use that, I was just using that as the example lol

#

sorry it's 7pm on east coast and I've been working since 7am lol

jolly kayak
#

My read of that Event is that the Account's "bank account ownership verification" is waiting for review and it ended up taking too long and causing payouts to be disabled

#

Part of the problem is still that since your own platform does not listen to account.updated Events, it's also tricky to read those Events (because of historical design reasons I don't trust them as much). That's an important thing you should aim to fix soon too

#

there are also important changes to account verification in the US that you might have been told about or working on which could have influenced that specific account

sturdy walrus
#

Well that's why I am wondering

#

We use the updated requirements, I am just confused why this account was disabled before the deadline

#

So I was looking to events to see if there was any warnings this account was gonna be restricted

jolly kayak
#

yeah something looks weird bug again the fact that you don't listen to those Events make it tricky to debug (I see a different version of the Event in our admin tools)

#

I don't know much about the new requirements and the rollout unfortunately so I can't tell you what exactly caused this specific one. You'd need to talk to support

sturdy walrus
#

Yeah just seeing who I should throw under the bus

#

Stripe or our eng team lol

jolly kayak
#

do you have another example I can look at?

sturdy walrus
#

Is there an event for bank account added

#

Yeah let me send the event before in the log

#

acct_1O9WvVPCk5hg7OiZ/events/evt_1OY92pPCk5hg7OiZZfoWxBAY

jolly kayak
#

no I mean another account

sturdy walrus
#

OOO

#

Yeah give me a sec

#

acct_1OZgTNPPUAGbUtQX/events/evt_1OoSNpPPUAGbUtQX9uypysoM

#

I see the creation

#

acct_1OZgTNPPUAGbUtQX/events/evt_1OZgfCPPUAGbUtQXgxGErQZG

#

There was no pending

jolly kayak
#

I'm sorry, struggling to follow your train of thoughts "I see the creation" "there was no pending"

sturdy walrus
#

Sorry I legit talk to myself sometimes

#

so that event shows that the account was created with no requirements

#

acct_1OZgTNPPUAGbUtQX/events/evt_1OoSNpPPUAGbUtQXIQQK7Gft

jolly kayak
#

what event? Sorry try to take a step back and write a clear summary in one paragraph/one exact answer

sturdy walrus
#

I think I got what I want but I'll explain what I am seeing

jolly kayak
#

That is not an account.updated. Did you look at the wrong Event type and mix things up?

sturdy walrus
#

The last few days we have been getting accounts suspended with no reason. I am trying to figure out why the accounts were suspended, and when they were also suspended. I was looking at the account.updated and saw that there was one event that showed no pending verification, then one 2 weeks later that disabled payouts, and added bank pending verification.

I then went and searched by account.external_account.created
to see if there was any verification when they created the account, which there were not. I then looked at account.external_account.updated and saw the most recent updated event was the same day accounts were suspended which means we were not alerted to the suspension until it was already suspended.

#

Also reading back my messages and I am so sorry, I legit made zero sense and sent like 50 events with zero context

#

No Pending Verification Event (account.updated): evt_1OZo3oPPUAGbUtQX3hYrUcRd

Pending Verification Event and Pay Lock (account.updated): evt_1OoSNpPPUAGbUtQX9uypysoM

Bank account added (account.external_account.created): evt_1OZgfCPPUAGbUtQXgxGErQZG

Account verification updated with pending verification (account.external_account.updated): evt_1OoSNpPPUAGbUtQXIQQK7Gft

jolly kayak
#

Gotcha, I see what you mean now. So is it fair to say that
You have some accounts that are suddenly becoming "Payouts disabled" due to some "bank account ownership verification" suddenly applying without any warning?

sturdy walrus
#

Correct

jolly kayak
#

Okay lol ugh

sturdy walrus
#

Customer just churned because of it

jolly kayak
#

Someone on my team randomly so our thread and it seems we did have a change on Monday the 27th about exactly that

#

and both events you shared are on the 27th

sturdy walrus
#

So by accident I am assuming

#

Doesn't seem like the best thing to change without notice if that was on purpose lol

jolly kayak
#

Not entirely sure if "by accident" or "announced but you didn't realize"

#

I don't know much about this sadly, I'm just seeing something internally about it. I would recommend reaching out directly to your point of contact at Stripe so that they can help investigate further

sturdy walrus
#

I got email from our account executive saying changes were happening on the March 15th

#

Yeah will contact our Rep

#

Thanks for the help!

#

Sorry for another Avery nonsense chat lol

jolly kayak
#

Totally fine!