#SebRollen
1 messages ยท Page 1 of 1 (latest)
Hi ๐
Currently Payment Links do not offer feature parity with directly creating Subscriptions or even using Checkout Sessions with Subscriptions.
At this point the only options you can configure are description and trial_period_days
Yeah, that's what I suspected from the docs. It doesn't seem like I can specify cancel_at_period_end using a Checkout Session either, right?
Even with Checkout Sessions you cannot specify cancel_at_period_end, yup
Okay, thank you. And if I create a Subscription directly, I need to first have a Customer and payment details specified for the customer, right?
I'm basically looking for a way to specify those extra subscription details without building the full payment form on our end ๐
Sounds like listening for the webhooks and updating the Subscription after it has been created is the only way to do that?
Currently yes that is true. We are working to expand capabilities regarding Subscription creation through Checkout/Payment Links but for now I thnk your webhook approach is the best way to achieve your desired outcome.
One question, if you are turning on cancel_at_period_end right after the Subscription is generated, why are you creating Subscriptions in the first place?
Since you are not collecting recurring payments?
Oh, good question.. I may have misunderstood how that feature works. What I'm looking for is a way to specify that the subscription should end automatically at the end of a subscription period, but to charge regularly before that. For example, to have the subscription end in a year, but to charge monthly between now and the end date
So maybe it's actually the cancel_at field I want to set
Yup! cancel_at_period_end will cancel the subscription at the end of the current billing period
If you want to test this out more thoroughly/rapidly I would recommend using Test Clocks
https://stripe.com/docs/billing/testing/test-clocks
That way you can advance time for a Test subscription and see how it behaves
Fantastic, thank you. I'm guessing that I will still have to set the cancel_at field using my webhook approach, since it's not a listed field for PaymentLink?
Correct
Thank you so much for the quick help @unborn plover, appreciate it!