mikeage_best-practices

[snow fog]

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

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

[glacial totem]

I thought about a webhook, but we can't know immediately how much to bill the user in any case, due to how our legacy backend works

[glacial totem]

(and yes, this means we have a similar problem on the last day of a billing cycle; we can't report their usage for that day because we don't know it until well after the period ends (the grace period is nowhere near enough). For now, we do it via two reports on the next day with an explanatory note; this is still an MVP, so it'll do)

[scarlet nebula]

Hmm I see. Just asking but could you (your business) modified to charge the pre-previous cycle, instead of the previous cycle? I mean effectively delaying 1 cycles. I know that is a big requirement changes.

ie you can communicate to your user that you will charge a fixed amount on April 1 for March usage, but you will recalculate it and charge the left needed amount on May 1

[glacial totem]

Perhaps I'm not understanding fully; how would that help? If they cancel the subscription on, say, Apr 15th, how do I bill them for April? Or do you mean that they'd pay on April 1st an amount that matches what their March bill was, assuming it'll be April's, and then we credit (or bill) for the difference?

My suspicion is that asking for prepayment (like a "retainer") wouldn't go over well with marketing in any case

The API doc at https://docs.stripe.com/api/subscriptions/cancel says that: "you could check for unpaid invoices before allowing the customer to cancel the subscription at all"

I didn't realize we could disable this feature. From Stripe's POV, is there any issue if we decouple the subscription from our service, such that the user cancels the service, we block further access, wait 24-48 hours, compute the final bill, and then upgrade Stripe's billing and then cancel?

Perhaps I misunderstood, but I thought a user could always cancel a subscription and we, as the provider, need to handle that

[scarlet nebula]

Yes that's correct understanding and I think it's ok for you to wait 24-48 hours before actually cancel the Stripe's Subscription, after you block their further access. But I can't speak for legal/requirements in your country for example. You could also just cancel the Subscription rightway, then later calculate the amount and send them a separated one-off Invoice