#wim_api

1 messages ¡ Page 1 of 1 (latest)

short pythonBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

timber lynx
#

Summary:
The invoice status changes from "Open" to "Void" after a user adds an insufficient card scenario if he attempts to create subscription in current month or resumes subscription manually.

Steps:
Buy a subscription with an insufficient card scenario
Navigate to stripe and observe invoice status
Advance 1 day
Actual result: invoice status on the 2nd step is "Open". After 3rd step status changed to "Void". The subscription and ticket have been deleted.
Expected result: invoice status is "Retrying" on the 2nd step. After 3rd step status is still "Retrying". Further advances should cause "Failed" status after several retries were made. Subscription should be still "invalid"

Test data:
customer: cus_RBG2rZHmiAGcfh

invoice: in_1QItXLBedPgr0Zv2v2DzEx9g

simulation link: https://dashboard.stripe.com/test/customers/cus_RBG2rZHmiAGcfh

bronze schooner
#

Hi, I'm taking a look here

#

From testing I believe this is expected as the first payment is not made within 24 hours so the invoice gets voided. So when you advance the Test Clock for 1 day, it's voiding the invoice as there is no successful payment on the first invoice.

timber lynx
#

but is there a way to not get the invoice voided? isnt there some past due state or something like this? additionally we dont want the subscription to become expired
i remember that there is a past due state too

bronze schooner
#

There is for subsequent invoices. The first invoice a bit unique in this way

timber lynx
#

hmm, is there a workaround for that? because this is critical for us

bronze schooner
#

There is not, you would need to create a new subscription

timber lynx
#

wdym by that? the subscription comes from a schedule doesnt it? how would we create a new subscription

bronze schooner
#

What do you mean by ' subscription comes from a schedule'?

timber lynx
#

ahhh got it

#

so you mean we would need to create a new subscription when the expired state is set

#

hmm, this is not really practical for us