#xqprtzcv_api
tawdry joltBOT
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.
- xqprtzcv_api, 4 days ago, 13 messages
- xqprtzcv_api, 5 days ago, 14 messages
- xqprtzcv_api, 6 days ago, 5 messages
sterile pivotBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1259949853283323994
đ Have more to share? Add details, code, screenshots, videos, etc. below.
arctic pebble
Interesting, I would think that that call would try to charge automatically. Does the invoice that that call creates stay in a draft state? The issue may be that the invoice needs to be finalized to attempt to charge the customer.
arctic pebble
Thank you, I can check in to that request in a minute
umbral bolt
I believe I may need to use "payment_behavior": "error_if_incomplete"
arctic pebble
Good catch! I do see that the subscription went in to a past_due on this update so that should result in an error with error_if_incomplete