Subscriptions

Hi there!

The subscription should work with the testing mode as well. But you would indeed need the webhook in place as per the documentation here:

Also, did you create the plan and associate the plan with a role?

There are a few ways to test Stripe webhooks locally, here is a discussion that covers this:

https://laracasts.com/discuss/channels/laravel/troubleshooting-stripe-webhook-setup-in-laravel-10-invalid-url-exception

One suggestion is to use the Stripe CLI and another option is to use https://expose.dev/

To grant a user a subscription, you can just change their role rather than actually creating an active subscription in Stripe and etc. Make sure to go over the docs here:

Wave subscription plans

Marking a post as "featured" doesn't automatically change its appearance or behavior. Instead, it provides a way for you to query and display featured posts as needed. For example, you can customize your homepage to only show featured posts. However, you'll need to add the logic in your views or controllers to make use of the "featured" flag.

Hope that this helps!

Once I successfully hit the endpoint by using https://expose.dev, the test checkout process worked when I subscribed as a test user. Cool!

However, if I were trying to grant access to a user as the admin by assigning them a role, it doesn't work. I am using the default roles and plans. The only thing I modified was I deleted the premium plan. I am trying to assign a user a basic role.

I guess this is because I gated some of my pages with middleware('subscribed'), but even if I assign a role to a user, that doesn't mean they are subscribed. I am guessing here, but if I check for role instead, it will work. However, what happens to a user's role when their subscription expires? Does it reset to registered, or does it stay at the expired user role?

Hi there,

However, what happens to a user's role when their subscription expires? Does it reset to registered, or does it stay at the expired user role?

Yes this should be the case, there is a webhook endpoint for this as well:

wave/src/Http/Controllers/Billing/Webhooks/StripeWebhook.php#L44

If you want to have some custom behaviour you could either change the middleware or update the subscriber() method on the user model to match your exact needs. For example if you want to grant user access to the app without them being a subscriber just based on a role, you could plug in that logic into the middleware or the method.

OK, so changing a user's role to basic, premium, or pro does not change their subscription status, so using middleware('subscribed') still blocks them? Also finally, is there any built-in functionality with the trial counter? And how is verified and verification code used? I see that it is separate from email verification.