justinsearls

[swift mist]

No worries. First of all, the use cases outlined in the doc above are really the only ones meant to be used with the pausing feature (ie. Offer services for free, Temporarily offer services for free and collect payment later, and Unable to provide services). The subscription remains active the whole time. If it's set to cancel at a certain date it will still cancel on that date even if sub is paused. We even say in that doc above that If these options don’t fit your use case, you might want to consider canceling subscriptions instead. Often cancelling is the right move. Then you can always create a new sub.

[solemn spade]

Ok, but this reasoning doesn't really square with the fact that customers are allowed to pause their own subscriptions from the billing portal by default. Why would the feature be there in the billing portal if the intent was only for merchants to decide to give services for free?

(I would disable this from my own portal except our customers and my product owner REALLY WANT to be able to pause their subscriptions as opposed to cancel them, I think due to the fact that cancelling feels more final psychologically)

@swift mist also that's an excellent handle

[swift mist]

Thanks

I'm actually not sure how the portal handles pausing off-hand

Have you tested in test mode?

[solemn spade]

Yes that's what I'm doing now. The portal seems to operate exactly like the document suggests

Adding that pause_collection property with the void option

It seems like two completely unrelated product features that share an implementation because they're both called "pause"

[swift mist]

Ah well if it handles it via the pause_collection property it is the same

But with the customer portal you can configure it to disable certain features

So if you don't want customers to have the ability to pause in that way, you can disable it

But yeah the way we handle pausing is the subscription technically is still active and continues to generate invoices

That's just how it is

[solemn spade]

Ok, thanks for clarifying @swift mist

So I can understand how to handle this in my app, does that mean that (1) I should immediately revoke service because upon un-pausing the user will reschedule their invoicing cycle or otherwise effectively "credit" them with any remaining time on their paid period or (2) I need to inspect their invoices to figure out myself when their paid period ends and revoke access after that point?

Thank you for your consideration or pointing me in the direction of where I can get an answer