Out of the box spark will always swap subscriptions - meaning if there is a new subscription added it will replace the current one.
Also the database is setup in a way taylored to one subscription at a time (e.g. consider the user table field current_billing_plan which only allwows one value.
I've also read someone talked about having to use the quantity attribute that Stripe has. So maybe my question now is what's the best approach in implementing multiple subscriptions using Laravel Spark?
@bkintanar Has anyone figured this out? We are improvising the same type of deal, multiple subscriptions within Laravel Spark, any references or examples would be awesome!
It falls short of an ideal solution because the user can't sign up for multiple plans, but it does offer a way to sign up for multiple instances of the same plan. (if that makes sense)
You do have to manually increase and decrease the quantity accordingly in your code to keep your records and Stripe's in sync