#itachi

1 messages · Page 1 of 1 (latest)

sweet bluffBOT
wide sparrow
#

Hello there

#

Hmmm

#

So your qualm with pause_collection is that you can't schedule it in the future?

spiral pier
#

yes. Also using pause_collection I will have to handle the proration as well. Like

if used subscribed on 1st May and paused the plan on 2nd May for 1 month. Now user wants to use the service on 28th May so he resumes the plan. Now using pause_collection integration stripe will charge user on 1st June with full amount. This isn't intended behaviour

wide sparrow
#

Okay

spiral pier
#

Am I clear ?

wide sparrow
#

Yep

#

Are you using trials at all?

spiral pier
#

nope. But i tried to integrate this using trials like when user pause the plan I am scheduling the phases which starts the trials and internally I am considering a plan with trial and a custom key in metadata {paused: true} as a paused subscription. this approach is working fine but doesn't looks a good integration idea

wide sparrow
#

That is what I was about to recommend

#

Why do you say "doesn't look like a good integration idea"?

spiral pier
#

because I was assuming that pausing the plan is a common use cause so maybe stripe provides a better and neat way to do so.

Adding custom logics are hard to maintain and can introduce bugs

wide sparrow
#

As you noted we do provide a way to pause the Sub :)... you use pause_collection

#

But yeah

#

This doesn't fit every use-case necessarily without some custom logic

spiral pier
#

yep.

Please correct me if I am wrong. I think pause_collection is there just to pause the payment when service provider either wants to provide free service or fails to provide services. It isn't designed with concept of using it as a feature which can be used to pause a subscription for user.

wide sparrow
#

I think that it is best suited as you described but it certainly could be used to pause a Sub.

#

Overall I think the trial route is the way to go here

#

Trials are used all the time to shift billing cycles

#

Very normal use-case for them to simulate a "pause"

spiral pier
#

Makes sense. thanks!

One more question. If I want to use pause_collection, than by adding custom logic I should be able to avoid extra charges to users.

  • pause the collection using pause_collection
  • when resuming. set pause_collection to '', billing_cycle_anchor: 'now', proration_behavior: 'create_prorations'

Also I need to schedule these changes. Is it possible to integrate something like this ?