Laravel Payment and Subscription Processing: PayPal & Stripe

In this class I show you how to get the latest version of Laravel, using Composer, along with some more details.

It is always helpful to have the source code of the course at hand, to answer questions and compare with yours in case of problems.

It is time to create the tables and models that will allow us to easily represent and use related information about the types of currency and payment platforms that the Laravel project will support

It is time to insert the main payment platforms to support (PayPal and Stripe) together with the main currencies (EUR, GBP, USD)

Laravel UI is a Laravel package that will allow you to quickly generate visual components that you will use in the course.

Let's resolve some possible confusion with the usage of Laravel Vite over Laravel Mix

In this class, you will take advantage of Laravel UI to get those visual components to use.

The components generated by Laravel UI work quite well, except that the styles are not there. So, it's time to put those styles and see how magically everything takes shape.

Now that all our views are using the same layout, we can add components that show success or error messages throughout the application.

The first field to implement in this component (a form) will be the one that contains the total value of the transaction. Of course, it can be randomly generated for ease.

Each transaction to be created can have a different currency type, so we will show the list of currencies supported by the platform through the Currency model in Laravel.

Finally, you should now allow choosing between the supported platforms, according to your PaymentPlatform model.

Each payment platform may require additional fields (such as Stripe), so in this class, you will give the form that ability to show or not certain fields according to the user's choice.

It is time to connect the form with Laravel. So, when you click on "Pay", Laravel receives the necessary information, to start processing the payment later.

Guzzle HTTP is a very useful library to send HTTP requests from PHP (and therefore Laravel). In this class, you will add it to the Laravel project using composer.

Now that you have Guzzle, it is time to create a generic component to use Guzzle and allow you to send any type of request, in addition to authorizing and decoding them accordingly for each service to be used.

Before you can use the PayPal API from Laravel, you need test accounts that allow you to act as a buyer or business that will receive money from a payment made with PayPal. Of course, they will be test accounts for the PayPal sandbox.

To consume the API, we need access credentials and you will get it with a PayPal application, which will be associated with a business account.

Once you have PayPal credentials, it's time to set up the online payment processing system with Laravel,

It is time to create a component (a class) that represents the PayPal service in the payment processing platform with Laravel.

The first step in using the PayPal API from Laravel is to authenticate correctly with the configured credentials and decode the responses obtained in JSON. That is what you will see in this class. In addition to seeing how everything works together.

You have already seen that you can send valid requests to the PayPal API. Now is the time to give PayPal the ability to create orders (directly using the API) to the service created.

Now that you can create orders using the PayPal API, it's time to see how to capture them, also through an API request. All after payment approval.

At this point, the PayPal service you created can create and capture orders in PayPal. It is time to communicate this with the created form so that the orders created correspond to what a user indicates.

Now that the order has been created and the user has been directed to the corresponding approval flow, it is time to capture that order and complete the payment processing.

We still have to implement a possible alternative flow, which corresponds to the case in which the user cancels the payment process at some point.

There exist some currencies which do not allow decimal positions. During this class, I will show you one and how to deal with it.

During this class, you will create the component that will be in charge of resolving the service related to a payment platform.

Once you have the component that knows the possible payment platforms to use. It is time to give you the ability to resolve the associated service according to what the user requires.

First of all, it is important to have an account in Stripe. In that way, you can obtain the credentials to access their API and monitor the operations of this account.

Now that you have your account in Stripe, it is time to get the credentials that will give you access to your API.

Once you have the credentials to access the Stripe API, it is time to configure and use it from Laravel, along with the base URL to use.

Finally! Now you are going to create the service that will know how to send requests to the Stripe API, using the configured credentials and base URL.

The first step in consuming the Stripe API is to know how to authorize requests and decode responses.

Before you can create an intent with Stripe, it is necessary to capture the data from the user's payment method, all using the Stripe JavaScript library.

Now that you have the payment method data, to avoid touching the backend with Laravel and complying with the SCA policies, you must resolve a token given by Stripe, which represents that payment method.