mike-connect | Stripe Developers | Page 1

tough vine Mar 30, 2022, 10:55 AM

#

I don't think it is possible. Do you have an example of the acct_xxx of the production one where that happened? Probably you contacted our support team and we did it manually or something.

harsh python Mar 30, 2022, 10:56 AM

#

Well, sorry to bother you, but it is.

#

You rejected one of our account's, and after our compliant you unrejected it.

tough vine Mar 30, 2022, 10:56 AM

#

quite possible! if you have an example of an account where it happened I can understand what went on and how you might simulate it in test mode

tough vine Mar 30, 2022, 10:57 AM

#

harsh python You rejected one of our account's, and after our compliant you unrejected it.

sure, that's what I said though? We can do things internally for support and operational reasons but there might not necessarily be a way to replicate that in the test mode API since it's not a normal flow.

harsh python Mar 30, 2022, 10:58 AM

#

I guess. But still, sadly, we have to modify our systems to unreject an account internally

#

I'll try to find the account.

#

Mind this happened about 2 months ago so there might be no logs anymore on our Stripe account

#

Anyway, is there any possibility someone from your end could unreject a sandbox account for us?

tough vine Mar 30, 2022, 11:01 AM

#

highly unlikely but you could ask our support team ( https://support.stripe.com/?contact=true ) !

#

speaking as a developer I would just treat this as a one-off and manually make changes to your database rather than trying to handle something like this programmatically. But I say that from an assumption that this was a case where there was an exceptional escalation involved, but I could be completely off, I have zero context here without looking at the specific example.

harsh python Mar 30, 2022, 11:05 AM

#

We have 3 clusters around the globe, a handful of microservices involved, a dozen of countries and thousands of accounts, couple of thousands coming more, so no, we can't do this by hand

#

I'm going to ask the support then, thanks.

tough vine Mar 30, 2022, 11:07 AM

#

ok!

harsh python Mar 30, 2022, 11:16 AM

#

So I have this account acct_1KMbKf2efwljkqsN

#

And the last update says it is rejected, but it is not (at the moment)

#

evt_1KaW9T2efwljkqsN9zmNX06K

tough vine Mar 30, 2022, 11:25 AM

#

yep so there's a few things

that account as far as I can tell was re-enabled by our risk teams after an appeal. That's a manual action using internal tooling. There's no way to simulate it in the testmode API itself. I wish I had a better answer for you then mocking the state or manually updating information, but I don't.
you're quite right that we don't generate a new account.updated event when that manual action happens, which I consider a bug and have raised many times. Someone is actually working on this at the moment, I spoke to them this week, so hopefully we'll fix that so that platforms get notified of the change in the account state.

Totally agree we don't have great answers here! I really wish I could give you a better answer, believe me. These are edge cases with how the Connect product and our risk operation interact and it's feedback I and my team do raise, I completely understand the problem here.

harsh python Mar 30, 2022, 11:27 AM

#

What will happen if a change is triggered now on this account, will it have the rejected.reason still set in the event?

#

Now as in "in this moment"

tough vine Mar 30, 2022, 11:29 AM

#

it would have the current status of the account, so it wouldn't show as rejected

#

basically the tooling changes the state of the account, and you can see that by retrieving it with a GET to v1/accounts, but we don't generate an Event/webhook

harsh python Mar 30, 2022, 11:31 AM

#

So, when the issue is resolved, we will receive an account.updated notification for every unrejected account. Am I correct?

tough vine Mar 30, 2022, 11:32 AM

#

that would be TBD and is one of the reasons we haven't made that change yet

#

we may or may not backfill events, that's TBD. IMO we probably shouldn't and won't, since in practise other stuff might have triggered account.updated since the unrejection so platforms would already have the new state; maybe we could try to only send them if there were no subsequent events but it's probably tricky to accurately identify that from our data. So yeah, TBD.

#

anyway, I wouldn't rely too much on that, I'm just sharing with you that you're not the only platform with this question, it's feedback we raise internally a lot, and at least recently someone has started looking at it. Something may or may not happen(but I'm going to raise this thread directly to help push for it). But in practise anyway, today this is an edge case with no great answers.

harsh python Mar 30, 2022, 11:36 AM

#

Where to look for such updates / announcements?

tough vine Mar 30, 2022, 11:36 AM

#

nowhere, we wouldn't announce this anywhere directly

#

again, I am not telling you we are 100% going to resolve this or anything will change.

#

I'm just being open with you.

#mike-connect