#naeem-ullah-khan_best-practices

1 messages · Page 1 of 1 (latest)

quartz coyoteBOT
#

👋 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/1341786408364277902

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

hollow sluiceBOT
bitter fractal
#

Hi there 👋 are you creating your Subscriptions so that they charge the customer automatically at the end of each billing period, or are you using the send_invoices value for the collection_method?

high swan
#

Hi, I'm creating subscriptions and setting a billing anchor cycle to 1st of each month and creating prorations so the users are charged every first day of the month. In the scenario that I mentioned in my question, I want to give a 14 days grace period for the community creators to resolve their payment issue within that grace period. After 14 days I want to pause the community's subscription with the platform and lock the community access for the community users as well

bitter fractal
#

Hm, so it sounds like you're talking about using the charge_automatically value for collection_method (default behavior).
https://docs.stripe.com/api/subscriptions/create#create_subscription-collection_method

Are you planning to use automatic retries for those failed payments? If so, you can set your desired retry schedule here, in the Manage failed payments for subscriptions section:
https://dashboard.stripe.com/settings/billing/automatic
or you can also enable smart retries there.

Then you can adjust the setting beside Subscription status in that same section to change the Subscription's status to past-due once the retry schedule is exhausted. Then your webhook endpoint can pick up on that subscription status change and adjust access to your service.

quartz coyoteBOT