Sign up to access "Build an E-Commerce Platform" right now.

So we're going to go ahead and attach the Stripe library to our container, we'll take a look around Stripe if you're new, and then we'll pretty much be ready to create payment intents and go ahead and charge the user at checkout. So the first thing that we're going to do is go ahead and pull in the Stripe PHP library, so let's go ahead and grab the composer

command to do this and pull this in, it's going to go ahead and install that for us, and then before we do anything else let's go ahead and grab our keys over on Stripe, so we can attach these to our config and then go ahead and pass these into Stripe when we boot it up. So if you don't already have a Stripe account of course you're going to need to go ahead and

sign up, and then you're going to need to come over to the test mode, toggle this. Now under the developers section here, add API keys, you'll find your publishable key which is used for the client side, and your secret key which is used for the server side. So we're going to go ahead and pull in both of these, we can hit reveal test key as well, and of course go ahead and enter our

password, and once we've done that we'll go ahead and see our secret key. So what we're going to do is come over and just create out some new config in here, so let's go over to our config section, let's create out a stripe.php file, and then from here we'll just build up a new config, so we'll just return an array, and we'll say secret, and we're going to use our environment

variables for this, so let's name them now, let's say stripe secret, and we'll just say stripe key, in fact we'll pump that to the top because usually we'll put the publishable key at the top, and that's just going to be stripe key. Great, so we want to pull both of these over to our EMV, let's do this at the bottom, stripe key, and of course stripe secret. Okay, let's go ahead and

grab both of these, so copy these over here, and we're pretty much done with our config stuff. So we can reference these if we head over to config, and I think it's under services, we can use stripe inside of here, or do what we've done and create our separate config file for this, it doesn't really matter too much, but we've got that in there now. Now the next thing that we need

to do is create a service provider so we can bind this to Laravel's container, and then we can use this wherever we like. We're going to do this in a really simple way and just bind it by a string, not to an interface, just so we can conveniently pluck it out of the container wherever we need. So for this we're going to go ahead and make a provider, we could do this an app service provider,

but let's go ahead and create a stripe service provider just so it is in its own provider, and let's go ahead and open up that stripe service provider under app and providers, and we're going to come down to the register section here, and we're going to go ahead and bind this in as a singleton. So let's go ahead and say singleton stripe, and then for this all we need

to do is create our closure, and then just return a new stripe instance. So for this we're going to go ahead and return a new stripe client which is from the package that we just pulled in, and then the only thing that we really need to pass to this for our use is the stripe secret. Now that we've created that stripe config we can say stripe.secret and that'll be pulled

directly from our env. So the last thing that we need to do is just come over to config and app and go ahead and paste in our service provider in here. So let's say stripe service provider, much like we did for our cart service provider, and we're pretty much done. That is stripe pulled in and we can start to look at processing payments on the checkout.