#maria-dabrowiecka_unexpected

1 messages · Page 1 of 1 (latest)

soft raftBOT
#

👋 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. Thank you for your patience!

⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.

🔗 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/1214895849532948501

📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.

valid gulchBOT
tawny whale
#

👋 happy to help

#

taking a look please give me a couple of minutes

tawny whale
#

this is expected because a new billing started on Feb 29

#

so the invoice was created then and then the payment failed a couple of times before succeeding finally on 3/4/24

flint cedar
#

okay, so new billing has started without successful payment - is this a standard scenario?
we've built our system based on different criteria - first successful payment from Stripe then we enter new billing period

#

I've seen users that first paid and then Stripe started new billing period

#

I had one case with a guy from India that had 26 hours delay because of location but this user is not from India

tawny whale
#

and finally the payment got through with the paid event you shared

flint cedar
#

okay, but so is it a standard scenario for all users to enter new billing period before charging with success?

#

another question is that - how can I tell what is possible duration of retries?

glass mountain
glass mountain
flint cedar
#

thanks a lot! 🙂

glass mountain
#

Happy to help.

flint cedar
#

The user was charged:
March 4th (succcess)
March 2nd (failure)
March 1st (failure)
Feb 29th (failure)

#

I wonder why the last retry (success) was done 2 days after previous one?

#

March 3rd was Sunday

glass mountain
#

Could you please share the Charge ID ch_xxx?

flint cedar
#

ch_3Op5okL7qyU6wPqu1X0stSr0

#

it's from March 4th,

ch_3Op5okL7qyU6wPqu1ERaqGWQ - March 2nd

#

ch_3Op5okL7qyU6wPqu1x9ZHYNX - March 1st
ch_3Op5okL7qyU6wPqu1XUD34tJ - Feb 29th

glass mountain
#

It was done on March 3, 22:41 UTC, that's why it might look like 4th on your side.

#

The March 2nd was attempted at 13:32 UTC

flint cedar
#

okay, I see, so let me understand why after cancellation the charge was performed?

#

We've sent cancel event to Stripe before final success payment, March 3rd

#

I would like to know what is the issue with the cancellation and how to perform it better (we expected user not to be charged after that)

glass mountain
#

Your customers already had a few days in the new period (Feb 29 - Mar 3), and they had to pay for it.
You can then void all the outstanding Invoices before cancelling the Subscription, but note that this will mean they have used your product for some days for free.

flint cedar
#

cancellation event: evt_1OqFv4L7qyU6wPquTqR3DBWa

#

I see that new period has already started but we wanted to perform immediate cancel without waiting for the period end, how can we perform this?

glass mountain