Laravel cashier checkout() does not save the subscription to the database

@vincent15000 yes, I have a route that handles Stripe's webhooks. Route::post('/stripe/webhook', [StripeWebhookController::class, 'handleWebhook']);

On Stripe's dashboard, I added this endpoint to the webhooks section. This route successfully fires on the events I'm listening for. also i listen to customer.subscription.created event as stated in the documentation. But I don't know how to handle it correctly.

public function handleWebhook(Request $request)
    {
        Stripe::setApiKey(config('services.stripe.secret'));
        $endPointSecret = config('services.stripe.webhook_secret');
        $payload = @file_get_contents('php://input');
        $sig_header = $_SERVER['HTTP_STRIPE_SIGNATURE'];
        $event = null;

        try {
            $event = Webhook::constructEvent(
                $payload, $sig_header, $endPointSecret
            );
        } catch(\UnexpectedValueException $e) {
            // Invalid payload
            logger('Logger Invalid payload');
            http_response_code(400);
            exit();
        } catch(\Stripe\Exception\SignatureVerificationException $e) {
            // Invalid signature
            logger('Logger Invalid signature');
            http_response_code(400);
            exit();
        }

        switch ($event->type) {
            case 'invoice.payment_succeeded':
                /*
                
                */
            case 'customer.subscription.trial_will_end':
            /*
            
            */
            case 'invoice.payment_failed':
            /*
           
           */
            case 'customer.subscription.created':
            /*
            
            */

            default:
                break;
        }

        http_response_code(200);
    }

@dev_2108 if you don't know how to correctly handle billing, then I'd suggest using Laravel's first-party package Cashier instead. That will handle pretty much everything for you from subscriptions, payments, and webhook. All you need to do there is use the provided functions it gives you to interact with it in your application.

@thinkverse Thank you. This is my first time working with subscriptions. That's why I'm asking for help... I am using this package, which you wrote about. My subscriptions are not saved in the subscription table that comes with the package. Subscriptions are created only on Dashboard Stripe.

@dev_2108 I have tested subscriptions without this package and it works fine just followed step by step the Laravel documentation.

@dev_2108 if you're using Cashier you don't need to implement the webhooks yourself. Cashier already comes with it built-in.

To ensure your application can handle Stripe webhooks, be sure to configure the webhook URL in the Stripe control panel. By default, Cashier's webhook controller responds to the /stripe/webhook URL path.

Reading on further in the documentation and it tells you which events to enable in Stripe, and which endpoint you should use, again it's: /stripe/webhook.

Do note that during development and testing, Stripe cannot call any localhost or .test sites that resolve to your local IP, so to test webhooks locally you need to either use the Stripe CLI to test your webhook endpoint or forward your local site using a service like ngrok or expose.

@thinkverse as I wrote above, I have a route in the project,

Route::post('/stripe/webhook', [StripeWebhookController::class, 'handleWebhook']);

which keeps track of Stripe's events. and the handleWebhook method of my controller works, the data sent by Stripe gets there, I can process it. I can't figure out what I need to do in order for my subscription to be stored in the database after this code

public function subscriptionCheckout(Request $request)
    {
        $user = auth()->user();
        return $user
            ->newSubscription('default', 'price_1N8z5gIXJCCFYtSmyBwtq4ih')
            ->checkout([
                'success_url' => route('dashboard'),
                'cancel_url' => route('home'),
            ]);
    }

should I write something in case, when the event fires customer.subscription.created

public function handleWebhook(Request $request)
    {
        Stripe::setApiKey(config('services.stripe.secret'));
        $endPointSecret = config('services.stripe.webhook_secret');
        $payload = @file_get_contents('php://input');
        $sig_header = $_SERVER['HTTP_STRIPE_SIGNATURE'];
        $event = null;

        try {
            $event = Webhook::constructEvent(
                $payload, $sig_header, $endPointSecret
            );
        } catch(\UnexpectedValueException $e) {
            // Invalid payload
            logger('Logger Invalid payload');
            http_response_code(400);
            exit();
        } catch(\Stripe\Exception\SignatureVerificationException $e) {
            // Invalid signature
            logger('Logger Invalid signature');
            http_response_code(400);
            exit();
        }

        switch ($event->type) {
            case 'customer.subscription.created ':
// here ?

@dev_2108 and as I wrote as well, you don't need to do that yourself if you're already using Laravel Cashier. It registers the route for you, handles the signature verification if the STRIPE_WEBHOOK_SECRET environment variable is set, and it creates the subscriptions in your database for you and handles charges backs, cancellations, etc. If you're using Cashier and want to react to incoming webhooks then subscribe to the events sent by Cashier.

If you really insist on implementing the webhook parts yourself, which is fine I guess. Though I'd rather use the battle-tested approach for peace of mind. What you need to do is parse the request, luckily Laravel has you covered there as well.

I don't know what Webhook::constructEvent is supposed to do, but verifying the signature is a breeze.

use Stripe\Exception\SignatureVerificationException;
use Stripe\WebhookSignature;

public function handleWebhook(Request $request)
{
        try {
            WebhookSignature::verifyHeader(
                $request->getContent(),
                $request->header('Stripe-Signature'),
                config('services.stripe.secret'),
				300
            );
        } catch (SignatureVerificationException $exception) {
            throw new Exception($exception->getMessage(), $exception);
        }

		// Webhook signature verified, begin parsing payload…
        $payload = json_decode($request->getContent(), true);
}

That's pretty much it as far as verifying the signature and parsing the payload into an array that you can then use to create, update or delete from your Subscriptions model.

You also need to be sure you're updating the right user, and you can do that by using Cashier::findBillable and passing in the Stripe ID.

$user = Cashier::findBillable($payload['data']['object']['customer']);

With that you can access the users subscriptions via the relationships and can now insert and update the related models.

And let me reiterate, you don't have you do this yourself, it's a hassle dealing with edge cases, and Cashier has you covered already.

@thinkverse thanks

@thinkverse Does Laravel Cashier register the /stripe/webhook route itself? And all I need is just to add this endpoint on Stripe's dashboard, and my subscriptions will be saved to the database on their own? did I understand you correctly?

my-domain /stripe/webhook

Does Laravel Cashier register the /stripe/webhook route itself? And all I need is just to add this endpoint on Stripe's dashboard, and my subscriptions will be saved to the database on their own?

@dev_2108 Yes, both me and @vincent15000 have been saying that since the beginning, it's all documented in the documentation for Cashier, which I linked above: https://laravel.com/docs/10.x/billing#handling-stripe-webhooks

@thinkverse I am having the same problem as OP after trying to use both the Stripe CLI and Ngrok - in both cases I get a 200 response from the webhooks and updated subscription info in Stripe's Dashboard.

Are there any other reasons why the checkout() method could fail to store user data in the subscriptions table?

Perhaps something wrong in the front-end? I am sending the user to the Stripe Checkout page through the /subscription-checkout route.

@MGT my problem was that in my project i created a route /stripe/webhook. And exactly the same route is in the Laravel Cashier package. And I, with my route, overwrote the package route. When I changed the url of my route, the route from the package started working correctly and saving all subscriptions. And don't forget to add webhooks, both your own and the package's, to the Stripe panel. And subscribe to the appropriate events from the documentation, @thinkverse posted the link above. I hope this helps you solve the problem

@dev_2108 Hi i read all your chat and its the same issue Iam facing that there is no subscriptions data entering to the database and its in stripe dashboard ,I have checkout controller code and handle same as like you and how did you solve it

@dimitriadis Are you calling checkout() on a user object? If not, see my comment below.