identity VS cashier-stripe

New identity sample: There’s a new Stripe Sample on Identity to demonstrate how to verify a user’s identity using both the in-modal verification and a full redirect to a Stripe hosted page.

Laravel Cashier Stripe v14.12.2: The latest version of Laravel Cashier Stripe , v14.12.2, focuses on improving the handling of the “payment_method.automatically_updated” webhook.

Laravel Cashier Stripe released v14.4.0 – v14.7.0, adding support for Laravel 10, stripe-php v10, and the latest version of the Stripe API.

Laravel Stripe released version 14.3.0.

Currently, Spark allow only to change your subscription, not adding new ones. Why is that? This was address already 2 years ago on Laravel Cashier https://github.com/laravel/cashier-stripe/issues/922

Laravel Cashier Stripe has released version 14.2 with support for guest checkout and a rebranded shipped receipt template.

Again, you don't technically need to store anything in your database. However, I recommend storing at least the string ID of the Stripe Customer (which looks like cus_abc123) in your database. You can store this directly on the users or teams table, or create a separate table for storing Stripe Customer IDs and their relation to PaymentMethods and Subscriptions. Maintaining a separate table offers a bit more flexibility later if you decide to change from supporting single users to teams. It also separates concerns. Have a look at the open source pay-rails database schema or the cashier-stripe migrations for inspiration for modeling your database. If you’d like more suggestions about how to model your database to work well with SaaS, let me know on Twitter: @cjav_dev.

Check out the latest updates to Laravel Cashier.

Versions 13.6.0 and 13.6.1 of Laravel Cashier are out.

Learn how to get started with Cashier Stripe and Cashier Paddle. [Video course from Dries Vints, co-maintainer of Cashier Stripe and Cashier Paddle]