#fdc8cd4cff2c19e0d1022e78481ddf36

1 messages ยท Page 1 of 1 (latest)

runic rainBOT
jaunty shale
#

Hi there!

#

You mentioned using billing_cycle_anchor. I think that's the correct approach. Did it work for you?

limber temple
#

Well for the option 1) yes, but I cant set the billing_cycle_anchor more further into the future than just next month ๐Ÿ™‚ Therefore it seems like its not viable for 2)

#

This is how it looks at the checkout with the trial

runic rainBOT
jaunty shale
#

Yes that's true. Then the trial period looks like a good option.

limber temple
#

To be fair not to me, it looks unpolished, since its not a real trial ๐Ÿ™‚

fickle dune
#

๐Ÿ‘‹ stepping in as soma needs to step away

limber temple
#

Not sure if its worth to mention, I am using your python sdk

fickle dune
#

The trial option is likely going to be the best option really. The other thing you could do is take a one-time payment initially and then start a Subscription using that PaymentMethod where you put the Sub on trial till you want to charge

#

Then you can use the description of the one-time payment to mirror what the Sub will entail

limber temple
#

Hmm, that also means there will be a trial mentioned on the checkout, am I right?

fickle dune
#

No you would create the Sub with the trial immediately after the successful initial payment

#

So that the customer does not see the trial on Checkout

limber temple
#

Hmm, if I understand that correctly, I need to get the user's payment method before that? I assume stripe.checkout.Session is the way to go for it?

#
  1. creating customer
  2. creating a session checkout for him (capturing his payment method) + paying for the one-time payment
  3. creating the subscription with his customer_id + payment method.

Is that correct?

fickle dune
#

Yep