#ass-_unexpected
wide harnessBOT
đ 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/1419633598629281813
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
past kraken
Having a look
Looks like your code (?) is manually paying the invoices ~5 seconds after creation: https://dashboard.stripe.com/test/logs/req_l1SHzZk3rNuwVj
Is that expected?
Likely a race condition where your pay request is sent before the job to void them (because of the pause) is ran
pseudo gyro
The pause was set immediately after the subscription was created (and the first payment), and in this subscription you can see that two invoices were created with the status PAID after the pause.
These invoices are generated by Stripe on their side, right?
past kraken
Did you look at the request log link I just sent? Your integration initialised the request to pay the invoice (in_1S95zcLU3SZk0W7hB22iVB4W) generated on 9/19 which was the first invoice after the pause on 9/17. Stripe did not automate the payment for that invoice
past kraken
The pause was set immediately after the subscription was created (and the first ...
An invoice cannot be created with a paid state
These invoices are generated by Stripe on their side, right?
Sure, we generated the invoices. But we didn't initiate the payment of them, your code did:
You need to understand why those API calls are being made, and stop them from happening
pseudo gyro
Got it. Thank you very much!