#viktor-zaunders_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1313874619433877598
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hi! yes, generally you'd do that by controlling the billing_cycle_anchor when creating the Subscription , with proration enabled : https://docs.stripe.com/billing/subscriptions/billing-cycle#new-subscriptions The default behaviour does what you describe of charging a prorated amount now, plus a fulll invoice later
I don't think this is possible using PaymentLinks, but if you create CheckoutSessions manually then https://docs.stripe.com/api/checkout/sessions/create?lang=dotnet#create_checkout_session-subscription_data-billing_cycle_anchor I think will work
thank you! you mean that creating CheckoutSessions manually is needed for setting the billing_cycle_anchor too? So for any method of acheving this we need to interact through the API?
yes all this is predicated on the idea that you are building a bespoke integration with the API rather than relying on a no/low code option like a PaymentLink