Seems Spark heavily promotes the subscription plan business model. I'm looking to rewrite a CakePHP application from ages ago and it bills per X and per Y. A user can have four X's and six Y's, for example. Can Spark work with this or is the fixed plan paradigm tied in heavily?
Neat, so I suppose each user could have two subscriptions?
// Sign up form
Number of foos for this account? 5
Number of bars for this account? 8
// Create user
$user->subscription('foo')->updateQuantity(5);
$user->subscription('bar')->updateQuantity(8);
This looks fine as long as Spark can handle whatever I throw at Cashier. I just don't want to buy it and end up fighting with it to work how I want.
I believe a user can only have ONE Plan at a time (at least that is the standard setup) but within that plan there is a quantity attribute that somehow can be affecting the payment (I think I read an example somewhere where a plan's price would depend on the number of users on a team) - but as said, i have not tried it myself.
I've just got through Stripe API docs today and @EventFellows is right, there is a quantity associated with the plan enabling you to do simple (price x quantity), not even (fixed + price x quantity), nor your (price1 x qty1 + price2 x qty2).