#dennis_de

1 messages · Page 1 of 1 (latest)

golden pythonBOT
jolly mango
#

👋 happy to help

#

would you mind sharing the event ID you didn't receive?

ionic tulip
#

Where can I find them? Otherwise I can give you the Connect ID, where you can also see in the API logs when the registration was and none is noted on the webhook.

jolly mango
#

is this in test mode or in live mode?

ionic tulip
#

Connect Registration Request ID: req_KbHvV0ZvWnoBD7

jolly mango
ionic tulip
#

Live

jolly mango
#

ok the request ID would suffice

ionic tulip
#

Webhook ID: we_1MawJKJZUpJ6fJ990QwGDrql

#

All other Connect registrations that trigger an "account.updated" can also be found there. Only not for this Connect account.

#

We then manually triggered an update this morning, here the webhook was sent out again.

#

Now, of course, we are wondering if it is normal that simply webhooks are not executed at all or if there was a temporary malfunction. Because depending on this, we have to build processes that will additionally check the lists.

#

Which we would like to avoid, of course, unless you advise us to do so, as that can happen.

jolly mango
#

I saw that the event went through and that your webhook endpoint responded with {"message":"Accepted"}

ionic tulip
jolly mango
#

yes exactly the first two events

ionic tulip
#

These are the activities in the Connect account. The request at 17:34 cannot be found in the webhook log, but the request ID (req_KbHvV0ZvWnoBD7) belongs to it.

Bildschirmfoto_2023-02-15_um_12.15.27.png
ionic tulip
jolly mango
#

oh sorry I might have missed something

#

taking a second look

ionic tulip
#

thx

#

I have now also found an event ID where you can also see that no webhook was created despite the type "account.updated".

ID: evt_1MbRPaR73Zr3QyMmSlYQJf5f

jolly mango
#

let me see

ionic tulip
#

Feel free to look at it at your leisure. I have to go to a meeting now. I'll answer you later.

jolly mango
#

yes I'll come back with an answer shortly, I'm still investigating

#

are these events that you're referring to happening while the account is onboarding?

ionic tulip
#

Yes, we normally get webhooks as soon as someone appears as a Connect account, i.e. registers.

jolly mango
#

exactly

#

so the event you shared was part of the onboarding

#

that's why you didn't get the webhook

ionic tulip
#

Just a minute, I'll find something.

#

I got the event ID directly from the logs of the Connected Account, of course the webhooks don't seem to be listed there. I'll see if I can find an event ID that is triggered for us.

#

Okay, so in our events you don't see the Connected Events at all, so that's not a clue. I'll keep looking to give you a concrete comparison.

crystal cedar
#

Hey, taking over here. Let me know if there's any follow-up Qs I can answer!

ionic tulip
#

Of none of the events, only one arrived in the "account.updated" webhook and we know this differently.

#

And that is precisely the problem... Normally someone completes the onboarding and the Connect account is displayed, you send the webhook and we process that. But here, not a single webhook has been executed.

#

As I said: Also recognisable in the webhook log

crystal cedar
#

Is there any difference of the onboarding of these accounts ?

#

are you using AccountsLink or Oauth ?

ionic tulip
#

No, at least none that I can recognise. The account was approved and created normally.

#

We use the links you can create via the Stripe Dashboard.

#

And as I said, we performed a manual update in the Connect account this morning and an "account.updated" event was sent directly.

crystal cedar
#

Thanks for these details.
So you are using Oauth onboarding flow. As far as the account is during the onboarding ( user entering information in the page) the generated event account.updated don't get sent to the platform. because the connection isn't finished yet.

crystal cedar
ionic tulip
#

I understand that, but there must have been at least one event that completed the registration and even that was not triggered via webhook.

#

We also receive an email as account owner as soon as the Connect account is registered and normally the webhook comes, which did not come.

#

We usually get between 1 and 2 webhooks on this shortly after registration, on this single account not a single one was sent and if we hadn't done a manual update it would never have been created in other systems.

crystal cedar
#

Yeah, that's one of the inconvenants of using Oauth. is the timing of the actual connection between the connected account and the platform.

ionic tulip
#

But we did that, didn't we?

crystal cedar
#

Can you share the link you are using in order to onboard your Connected Accounts ?

crystal cedar
ionic tulip
#

But even if it did, didn't it work for all the other accounts? It's always the same procedure.

crystal cedar
#

This is the Oauth approach and it's not recommended. You should be using AccountLinks for more accurancy.

ionic tulip
#

So I understand the statement that you recommend a different procedure, but it doesn't change the fact that it worked for all the other 7 accounts and only for one account it didn't work.

crystal cedar
#

That's the drawback of using the Oauth approach, the timing of the connection is not always the same.

ionic tulip
#

It is not equal, correct but no webhook was sent at all if we had not manually triggered it.

#

I also don't think that the problem necessarily has anything to do with what was used to create the account, as it worked perfectly with other accounts. The fact is that the account was connected, the email came normally (*@.com is now connected to your platform) but no "account.updated" webhook was triggered.

#

It can't be that even if you don't recommend the process, that you offer the possibility to create a link via the dashboard, which in exceptional cases should not trigger a webhook when the account then registers? The explanation is lame.

crystal cedar
#

I just double checked with my colleague and that's what they confirmed too.

correct but no webhook was sent at all if we had not manually triggered it.
You can try to update the connected account again and you'll get the webhook event. But during the onboarding events may not be triggered when using Oauth.

ionic tulip
#

So why did it work for everyone else?

#

As I said, it worked for 7 out of 8 accounts without any problems. As soon as the Connected Account was successfully connected, a webhook was transmitted.

crystal cedar
#

The timing of the connection is not always the same using the Oauth. that's doesn't mean it happens all the time.

ionic tulip
#

What does timing have to do with it? I know that when the user clicks on the link, no webhook is sent, but when the account finally appears on our site is relevant.

#

I'm not sure you've really understood the problem.

crystal cedar
#

What does timing have to do with it?.....but when the account finally appears on our site is relevant.
If the event was generated before the connection is done (the account appears on the dashboard) then you won't get the event on your Platform webhook.

ionic tulip
#

So why do you offer this method in your Stripe Dashboard? This sounds more like a procedural error in your own implementation?

#

But how can it happen that the event is generated before the connection is completed?

crystal cedar
ionic tulip
#

We have received 2+ webhooks for all other accounts, but none at all for this one. If it was just the order of the first one that triggered an event before the connection, ok, but if the account is connected and that doesn't trigger another update that we get 100%, something doesn't fit for me with them yet

rancid girder
ionic tulip
#

I understand. But that doesn't change the problem that the respective platform is flying blind and would never have noticed this account if we hadn't noticed it manually. If necessary, the account would have logged in again and changed its data. That can't be right, can it?

ionic tulip
rancid girder
#

I'm not sure what you're referencing here

ionic tulip
rancid girder
#

So its expected your Connect webhooks would not receive any events from the account during onboarding

ionic tulip
rancid girder
#

I can't speak to your other account(s) without examples. But, as noted, OAuth onboarding is considered legacy for reasons exactly like this

rancid girder
ionic tulip
#

When the email arrives at the platform that a new account is connected, shouldn't an "account.updated" event have been executed there?

#

So the email that Stripe sends

rancid girder
#

Maybe? I don't know what email you're referring to, nor do I know exactly when that is sent

ionic tulip
#

E-Mail ID: em_nlejhvgnh1oaiarfrg2gwg2xersgp2

#

I appreciate you very much and also your help. But I don't think the problem is related.

#

Shall I give you another case where it worked without any problems? So that you can compare them?

rancid girder
#

I'd recommend speaking to support regarding this. This isn't a technical/integration issue we can help with directly here, nor is it something you can configure. It's just a limitation of the OAuth onboarding flow that myself and colleagues have noted. This is why its considered legacy and new platforms should use Account Links instead where this isn't an issue.

ionic tulip
#

I can of course contact support in the hope that they understand. From my point of view, the webhook was simply not fired.

#

We will continue to monitor this and of course take into account the advice to change the implementation.