[L4] Cashier handleInvoicePaymentFailed not getting called

*** Update ***

Adding a check into the handleWebhook() in my WebhookController allows me to call my own handleInvoicePaymentFailed() like so:

<?php

class WebhookController extends \Laravel\Cashier\WebhookController {

    public function handleWebhook()
    {
        $payload = $this->getJsonPayload();

        if( $payload['type'] == 'invoice.payment_failed')
        {
            $this->handleInvoicePaymentFailed($payload);
        }

        // Fallback to failed payment check...
        return parent::handleWebhook();
    }

    // This never gets called
    public function handleInvoicePaymentFailed(array $payload)
    {
        // // This never happens
        $company = Company::find(1);
        $company->active = 0;
        $company->update();
      
        return new Response($payload, 200);
    }
}

Is a better way to do this - it feels like a bit of a hack.

Hi @appnorth like you I'm using the Company model for my Stripe subscriptions, but instead of adding an active field to the companies table, I chose to use the Cashier expired() method on an App::before() filter, like so:

if(Auth::check())
{
    // ...

    if(Auth::user()->company->expired()) return redirect(route('logout'));// I flash a message as well

    // ...
}

Wouldn't that be better for you as well?

Hi nikospkrk

Thanks for your reply. I have only just seen it.

I don't suppose you can provide any more code around your solution?

Also, when the 'invoice.payment_failed' is sent from Stripe what should that actually do in the database? I had assumed that it would cancel the account in Stripe and add a 'subscription_ends_at' date in my database, that doesn't seem to happen. Im not sure if thats because i'm in Test mode at the minute or something else.

The thing is, with my system I need the user to be able to login but restrict what they can do after the 'invoice.payment_failed' event has occured. So for example, they can only access a single view which will inform them of the payment failure and a way to rectify it.

Thanks again.

\Laravel\Cashier\WebhookController@handleWebhook checks if the event really exists - thus TEST hooks will NOT be handled

        if (! $this->eventExistsOnStripe($payload['id'])) {
            return;
        }

Comment out return; and you'll be set for testing.

@Francismori7 Your reply just saved me a ton of time. I absolutely could not figure out why my test webhooks weren't calling my extension functions!

@aaronhuisinga Believe me, it did to me too!

If you look in the Stripe account settings under "subscription" you should see how stripe handles failed payments, it retries them over a few days by default, you need to change this to

1st failed attempt: Stop trying to collect payment and... Then finally: Cancel subscription

This will send the Subscription deleted hook and trigger the CustomerSubscriptionDeleted function (which comes default with Cashier) This function should update your database and set Stripe active to false on the model and everything else.

I am using L5.1 and just went through this exact thing and what I found, at least in the version of Cashier that I'm working with, is that this code block:

        if (! $this->eventExistsOnStripe($payload['id']) && ! $this->isInTestingEnvironment()) {
            return;
        }

Will cause the method to do nothing and return nothing because the event id in a test webhook is not a real event id, and the second part will also evaluate as true unless you add the following to your .env file:

CASHIER_ENV=testing

as discovered by looking at the isInTestingEnvironment() method.