#fpereira_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1254788643877290046
๐ Have more to share? Add 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.
- fpereira_invoice-pdf, 3 days ago, 9 messages
- fpereira_api, 3 days ago, 6 messages
Hi ๐ can you share the ID of the request returning that error?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
we'll look for it
This is the id in_1PP4SV09nSxG3OSLhXi7qntZ, my team confirm that the endpoint return this error was POST v1/invoices/id/pay
I'm a little confused, you said you weren't able to create an Invoice but shared the ID of an Invoice object.
There wasn't a default payment method set on the Customer at the time you made that request. There is now, does the error persist if you try that request again?
๐ stepping in
So looks like https://dashboard.stripe.com/test/logs/req_R1ikQGZ6Mq4IB7 is the error you are referring to
It looks like you updated that Customer to set a default payment method after you attempted payment. You did that here: https://dashboard.stripe.com/test/logs/req_Y0enqpnb9TZGw6
So if you try again you should now see it work
Thank you a lot, we'll do some test and if it's necessary we'll contact support again