#gecko-trial-epoch
elder coyote
@digital mantle just in case I can get ahead of the question: yes all timestamps in the API are unix timestamps
digital mantle
🙂
good try, not it
i read that part already 🙂
so trial period ends on an epoch...so 1 millisecond after the trial period ends, the invoice happens?
(i'm trying to make sure I code "when" I want the trial to end...not that your system is <1ms accurate 🤣
elder coyote
(for the future, please just ask the question upfront in one message, way easier :))
And no that's not how it works. The period ends and then we will create the next invoice asynchronously and that can take a few hours
digital mantle
ok...is there an actual time commitment for how long this takes? for digital services, that can mean a disruption?
elder coyote
no commitment no, you really need to build your system differently. You can't cut off access at the exact second of the period end
you have to wait for the renewal. the failed payment, etc.
digital mantle
that's what I'm trying to understand...what's the "grace period" I should assume here?
elder coyote
multiple days
I would rely on the events being sent when things renew and likely buffer a few days, especially if you let people retry failed payments
digital mantle
I would rely on the events being sent when things renew and likely buffer a few ...
is there something more "immediate" like an event that signals renewal beginning or something before invoice creation that I can anchor on, or do I need to manage these times totally on my side, without event knowledge?
zinc sable
Hello @digital mantle stepping in and gimme a min
Let's go back that what do you plan to do with that timestamp?
If you just want to know when a Subscription renew, you can look for its current_period_end
digital mantle
right now I have a monthly subscription, that ends on the last day of the calendar month
and I want renewal to happen at 00:01 UTC on the 1st of the next month
with one time payments, it's immediate, and if the person is awake at this time, it will be initiated by them and the transaction happens at this moment
I'm trying to understand the lead/lag time for subscription renewals, so I can handle this and not have disruptions
zinc sable
You can control the billing cycle date
I think this is what you want: https://stripe.com/docs/billing/subscriptions/billing-cycle#new-subscriptions
digital mantle
You can control the billing cycle date
no, I don't need to know about how to set the date, I figured that out.
if....renewal is on the 1st, and Stripe takes days to send me a payment received event, then right now I have a customer that has a subscrption, without payment to me, and I'm trying to understand how long of a grace period I have to build in....or if there's an "event" I can key off of, that YOU initiate at renewal time, that lets ME know that the renewal has begun
zinc sable
How long of a grace period is hard to tell. It depends on the customer, ie. how long they can provide a new payment method in case their registered one is errored. But once they have you will receive an invoice.paid event
TLDR; when you Sub renews, we will send an invoice.created event. Once the customer successfully paid the invoice we will send an invoice.paid event
digital mantle
and if I understand right, the invoice.created event is "hours" after the renewal epoch triggers. yes?