#andres-chalarca_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1242107898662748299
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there ๐ I don't think I've seen that error before, so I'm not exactly sure what led to it. It seems like maybe the Invoice's payment attempt encountered an error.
makes sense, but, I'm not trying to pay the invoice, I'nm trying to mark it as uncollectible without trying to pay it.
Hm, I see this is a testmode Invoice, are you consistently able to get Invoices into this state? Are you able to void the Invoice instead?
Well, this is a new use case. So, I haven't marked invoices to this status before. When I mark invoices as void it works.
Gotcha, I'm still digging to see if I can spot why this may be happening.
thanks in advance!
Sorry, nothing has been jumping out at me.
๐
๐ taking over
We are looking @ember lark and we'll circle back
Looks like the Invoice got into a weird state
But we are figuring out why exactly
ok
Alright yeah it looks like trying to pay the Invoice with an ACH Credit Transfer source that wasn't chargeable put the Invoice in a weird state. We are filing a ticket internally to prevent this from happening in the future, but assuming you don't attempt to call /pay using that ACH CT Source (which is set as the Customer's default_source and thus why it was used in the attempted payment) then the Invoice should be fine to mark uncollectible.
If you are testing a specific flow out then I'd recommend creating a new Invoice and testing again