4 ms·
It's awesome this feature is supported (I've seen some cases where it's needed) and that Stripe is so responsive to their customers. FYI Recurly supports this a
by callmeed 13y ago
It's awesome this feature is supported (I've seen some cases where it's needed) and that Stripe is so responsive to their customers. FYI Recurly supports this as well.
Just remember, if you have customers on 2 subscriptions, you're losing 30¢ by charging them 2x instead of one. If you find yourself with lots of customers on 2 subscriptions, it might be worth it to rethink how your plans are structured.
- drx 13y agoIn most cases, 30¢ is worth the reduced headache.
- timdorr 13y agoDoes Stripe not combine the charges for multiple subscriptions into one charge? I think that would be pretty smart.
- jdanz 13y agoFor the v1 of multiple subscription support, we don't combine subscriptions into one charge. Hopefully we didn't get a biased sample, but we asked some of our beta users about their preference here and the consensus was for keeping each subscription separate -- per-subscription invoices, and thus per-subscription charges. At the very least, this is likely the simplest thing to reason about, in terms dunning and various unpaid / past due states. I could definitely see us allowing lumping subscriptions into one charge, at least as a configuration option. One thought is that the right solution might be to support specifying at creation time that a subscription's billing cycle should 'snap to' another's, leading them to be invoiced and billed jointly going forward. Would definitely be happy to discuss these use cases more -- jim@stripe
- rpedela 13y agoI am a new Stripe user who is just about to finish implementing a workaround for the limitation of one active subscription per customer. I was excited to see this news, but my excitement was tempered when I read that billing for multiple subscriptions is not consolidated. I would love to see consolidated billing support with multiple subscriptions (configuration option is fine). Until then I will keep my workaround since it does what I want for my customers.