#gosborn
amber umbra
magic crown
Hi there! This all sounds correct
I was going to call out the charge_automatically piece but you accounted for that
earnest solstice
Hey roadrunner! Just trying to calm some anxiety that I'll be getting in a year when these Subscriptions renew 😆
magic crown
If you haven't already, I recommend creating a simulation with test clocks: https://stripe.com/docs/billing/testing/test-clocks
earnest solstice
charge_automatically is set to true when creating a Subscription via the API, correct?
magic crown
correct, charge_automatically is the default for collection_method
earnest solstice
right - sorry, forgot that was an enum
magic crown
Test clocks make it easy to advance time, so you can create a subscription and fast forward to 1 year later to see the test charge go through
earnest solstice
Cool - so having a Subscription with "charge_automatically" as the collection_method + seeing the PaymentMethod as "off_session" should be enough to know that the future behavior will be to charge at renewal?
Or just seeing something in the "Set up for future use" field for a Payment method in the dashboard? Or is "set up for future use" not that necessary after a charge goes through?
magic crown
In your scenario, the collection of the payment details through a SetupIntent is what will allow you to automatically start and charge for a subscription without the customer's involvement
that said, you should only use a SetupIntent if you plan on creating off-session payments for these customers outside/in addition to the subscription charges, or if there's a gap of time between the collection of the payment details and when you want the subscription to begin. otherwise, I recommend collecting their payment details at the same time as the subscription creation - https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements