#Eli
1 messages · Page 1 of 1 (latest)
Where are you driving these statuses from? They don't align with actual possible statuses: https://stripe.com/docs/invoicing/overview#invoice-statuses
Sorry, poor choice of terminology on my part! What I mean by derived status is essentially a state that invoice is in. Example attached. Thanks
Ok, so the Dashboard label. They don't directly map to a single field in the API, nor am I sure how that is computed exactly. I would say your guesses are largely right except for the debit_card specificity? Not sure why you're limiting to that or where you're find that field
As I can see from history, the debit_card limitation/check was added due to the direct debits having no "retrying" state, thus no next payment attempt but then it can also be in the state of attempted while the charge is processed by the customer's bank. This incorrectly forces the invoice into a "failed" derived state that can be misleading for our platform users. It is a bit confusing, hence the initiative to understand the logic behind those labels so we can replicate it our UI to reflect the source of truth (Stripe in this case)
Yeah but which API field are you checking for that debit_card field? Because that's not an enum value in our API AFAIK
We just use debit: https://stripe.com/docs/api/payment_methods/object#payment_method_object-card-funding
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.