#play3r_connect-webhooks

1 messages ¡ Page 1 of 1 (latest)

grizzled canopyBOT
#

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

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

loud quail
#

My main goal is to know, when to redirect user where.

Currently I check:

  • User doesn't have connect account > Create one
  • User doesn't have submittedDetails > Redirect to onboarding
  • User has submittedDetails > Redirect to dashboard

I believe this is the correct way to do it, however, as I mentioned in above, I'm struggling to get a notification about the submittedDetails field.

dark pagoda
#

Hello! To clarfy, are you not getting any account.updated Events for your connected accounts? Or are you getting some of them?

loud quail
#

I've created the account, onboarded it and even try to onboard it again and change some values, I didn't get a single one.

image.png
grizzled canopyBOT
loud quail
loud quail
dark pagoda
#

Ah, it sounds like you only have a normal Webhook Endpoint set up. You need a Connect Webhook Endpoint to recieve Events from your connected accounts.

half maple
#

play3r_connect-webhooks

loud quail
#

Oh, that would make sense, this makes it easier to differentiate between normal and connect-related webhooks as well, will try it out right away!

half maple
#

sure thing

loud quail
#

Just to make sure, my approach is correct, given that the webhook hits?

half maple
#

not sure I understand your question

loud quail
#

I meant if my logic for figuring out where to redirect the user based on the conditions I explained above makes sense and if it is the correct approach, first time working with Stripe Connect.

half maple
#

I would say yes. Sorry the question is quite vague right now so it's hard to really grasp what you are asking

loud quail
#

I understand, let me clean it up, so it's easier to understand.

Basically, I'm letting my users choose to become a Creator - sell subscriptions.

I have a button, that redirects the user to different places, depending on certain conditions (conditions of in which state their Stripe Connected account is in right now)

  1. If the user doesn't have a Stripe Connect account linked to their profile, we create one.
  2. If the user has a Stripe Connect account linked, but doesn't have the detailsSubmitted set to true yet, we redirect them to the onboarding page.
  3. If the user has the detailsSubmitted set to true, we redirect them to the dashboard.

We only check if detailsSubmitted is changed to true, we are not expecting it to ever change back to false, we expect that once the user goes through the onboarding stage, it is safe to always redirect them to the Dashboard, with any upcoming requirements being handle by Stripe. (We use the Express account mode)

--

Now, would this be the right approach, or is my understanding lacking/wrong?

half maple
#

yeah checking detailsSubmitted doesn't really make sense to me

#

But I guess I need a crucial bit of information first: What type of connected accounts are you using?

loud quail
#

Express

half maple
#

Okay so what do you mean by "send them to the Dashboard"?
And do you understand that there's a lot more to identity verification than just detailsSubmitted? It's totally fine to say no by the way, I'm trying to figure out where you are in this

loud quail
#

By sending them to dashboard I mean redirecting the user to their Stripe Express Dashboard.

I understand that there are multiple steps of verification when it comes to business, identity and other topics required, however I was hoping that all of this would be "abstracted" by using Stripe - eg. we only care if user was onboarded, Stripe can handle the rest.

half maple
#

yeah that's not really how it works. I mean we handle most of it but as a Connect platform you absolutely want to understand how it works, when additional data is needed from them to nudge them, when their Payouts or payments are disabled, etc.

loud quail
#

I was hoping that redirecting them to their dashboard would show them some type of notification about missing details, if that's not the case, how do we fix missing required information?

According to this article: https://docs.stripe.com/connect/handling-api-verification, I was hoping that we wouldn't have to do much. (as lazy as that sounds)

Do I just send them back to onboarding, where they will be required to fill in the missing pieces?

half maple
#

yes you should send back to onboarding with an AccountLink in that case. And as a platform you should listen for account.updated Events, keep track of what is inside requirements for each connected account and make sure you nudge them to come back to fill the information before they get their payouts or payments disabled

loud quail
#

Alright, so my flow was somewhat correct, I just won't be checking the detailsSubmitted, instead I will be checking that requirements.currently_due is empty, if not, I will redirect the user to onboarding.

#

At least that's the simplified version, of course I will have to handle informing the user on what is going on, what to do, etc.

half maple
#

look at past_due too

loud quail
#

Alright, if I understand it correctly then, if past_due contains anything, the account is also disabled?

half maple
#

the account is not disabled itself, but some things could be such as Payouts being disabled yes

loud quail
#

Okay, that makes things clearer for me then, however, back to my original issue, I'm still not getting hit by the account.updated event, even after creating webhook of type Connect, going to the onboarding link and changing things.

half maple
#

Happy to help with actionable details! Please share exact code, the exact account id and what you see

loud quail
#

Nevermind, it just didn't load properly, because I got logged out after going through the onboarding. My bad, it works fine now, thanks again for explaining the flow of Stripe Connect better for me.