Sign up to access "Build a File Marketplace with Laravel" right now.

our Stripe onboarding controller called redirect. And we're going to go ahead and set up a route for that as well. So let's just copy the onboarding down here, and that's slash redirect. And remember, that's the link that we gave over here as well. So as soon as we click on this, we'll go through to here. So let's go ahead and switch the method over here to redirect.

And we'll set this as onboarding dot redirect, just so we have a reference to the name. Okay, so to do this, what we're going to do is go ahead and maybe just choose response here as the variable name. And we're going to go ahead and grab Stripe out of the container. We're then going to access the account links part of the API. And we're going to go ahead and create

one of these. What this will effectively do is give us back a link object, we can grab the URL from that and then just redirect the user over to that. So what do we need to pass into this, there's a couple of things. The first thing is the Stripe account of the user. So again, we can use our request if we just bring that into the controller here to grab the currently

authenticated user. And we can go ahead and grab their Stripe account ID. That's what we created in the last episode, when we registered. The type of link here is going to be an account onboarding link. So this is account underscore onboarding. And then we just need two more things to get this working. We need a refresh URL, which is going to be redirected to if something goes wrong,

that's just going to be redirecting us back to this onboarding flow. And we need a return URL, which is what happens when we have successfully gone through the whole onboarding process within Stripe. And we come back to our account to verify this. So the refresh URL is basically just the redirect that we've just created. So we're going to generate our route if we just head over

to our web route back to onboarding redirect. So if something goes wrong, we just put the user back into this redirect flow. The return URL, which we haven't got at the moment, is going to be something like onboarding and verify. So this is where when the user has successfully gone through the flow, we redirect them back to this page, we verify that they have successfully set up for payment,

and then we enable their account. So we'll create this page out now really quickly so we can see this entire flow just before we go ahead and redirect the user. So let's go ahead and create out another method inside of here called verify. And it's just die dump here and just say verify for now just so we know that this works. We'll go ahead and create a route for this as well. So

again, it's just a matter of copying and pasting this down, heading to verify, choosing verify as the name and switching the name over here as well so we can reference it. Okay, so now that we've done that, the response we get back from here, let's just die dump on this just so we can see what this contains. So if we head over here and we click connect with Stripe now, that makes a

request. And yeah, at the moment, I've probably spelled account onboarding wrong, a bit unboarding, so that would make sense. Let's try that one more time. And there we go, we get back this account link object. So this doesn't contain much, but the thing that we're interested in is the URL just here. So really, all we need to do at this point is just return here a redirect. And we want to

redirect to response and URL. So now effectively, when a user clicks on this, they are forwarded over to Stripe to complete the onboarding flow that we saw in the introduction. So I'm going to go ahead and click on this now. And once that gets generated, we get redirected over and you can see here exactly what we saw in the introduction. So I'm going to go ahead and fill this out. And I'll

be back with you in just a second before we see how this redirects back over to our app. Okay, so I've gone through all of the onboarding steps and we're at this page that we saw in the introduction where we can review our details and agree and submit this. So now when we agree and submit, we'll be forwarded back over to our app, to this verify page, which we've created out here

and registered a route for. But at the moment, obviously just dies and dumps and should just say verify. So there we go. Now it's at this point, we will hit the API again and verify that the user has payments enabled. So we can actually start to process payments and they can receive payments and we can receive a cut of that payment.