#Jogui-Subscription
1 messages ยท Page 1 of 1 (latest)
yes!
the first subscription: https://dashboard.stripe.com/subscriptions/sub_1KmcoVHFmluYEPgfMPDc3xXQ
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
(check event logs between 1:52PM and 2:53 PM)
and in this timespan, the user bought a second subscription, due to our implementation, which in that timespan, had no valid active subscription:
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
I was wondering if like Google Play subs or Apple subs, there's a setting or something to make Stripe generate the new invoice of the subscription 1 day before or something, not just at the same moment it must expire: https://dashboard.stripe.com/events/evt_1KrhVMHFmluYEPgfKtdjgfP4
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
OK, I can see the status of the subscription transitioned from trial to active, and there's only attempt to pay the invoice and it was successful.
After the invoice is created, Stripe will wait one hour and then finalize and charge it. That's why you saw the invoice was paid one hour later, this is the expected behaviour.
Stripe doesn't stop the customer to purchase the same subscription again, but you can decide to stop the purchase if the customer has already subscribed.
Okay, then I have to consider in my implementation, that "After the invoice is created, Stripe will wait one hour and then finalize and charge it. That's why you saw the invoice was paid one hour later, this is the expected behaviour."
is always 1 hour aprox right?
I thought it was instantaneous, and by several specifics of our implementation, during this hour, the user has no service and the checkout page is available to them again
If you see the log, the subscription's status was already active when the invoice was created.
Yes, the point is that we don't take fully acocunt of this value, but we also take account of the last_invoice.status
anyway, with that information, it's more than enough to fix the problem! ๐
One last favour, please: Can you validate me that is one hour between the invoice start and the charge? Is this for all subscriptions?
(Given the current situation, I will give to the specific point of our code, some hours of internal "grace period" to close this time-windows between subscriptions and go on).
That's the standard behaviour for all charge_automatically invoices, it's also mentioned in the doc (https://stripe.com/docs/billing/subscriptions/webhooks#understand)
Woah, perfect! Very happy to hear that
thank you to enlighten me in this monday morning
lets start the week optimistically hahaha
Also take note on the invoice.created response if you are listen to this webhook event type
okay
also found this:
After your first invoice, the following cycle of events repeats every billing period:
A few days prior to renewal, an invoice.upcoming event is sent. The number of days is based on the number set for Upcoming renewal events in the Dashboard. You can still add extra invoices items if needed.
When the subscription period elapses, an invoice.created event is sent, indicating the creation of a draft invoice.
About one hour after the invoice is created, it is finalized (changes are no longer permitted), and an invoice.finalized event is sent.
A payment is attempted, and payment_intent.created and payment_intent.succeeded events are sent to indicate that the payment was successful.
perfect, thank you ๐