#jamon
1 messages · Page 1 of 1 (latest)
Hello! Do you have an Invoice ID showing the issue I can take a look at?
in_1M1d9mIeTJrsS1reBk9s0ame
Thanks, looking...
This is a one-off Invoice, it's not subject to the settings you mentioned because those settings only apply to Subscriptions and the Invoices associated with them, where failed payments are retried.
hmm so that settings page is only for subscriptions? So one off invoices are left as is?
In this case it was incomplete though
and it has been more than 1 day
i am surprised it is not across the board one time and subscriptions
That setting is only for what to do after an Invoice's automatic retries have all failed, but one-off Invoices do not have automat retries as they're not for recurring Subscription payments.
If you want a one-off Invoice to be marked as uncollectible you need to mark it that way yourself based on whatever criteria you wish: https://stripe.com/docs/api/invoices/mark_uncollectible
Wow. So if I have a stripe checkout subscription that was 3DS and failed authentication, then I make a new stripe checkout session and successfully pay the new session, what happens to the old failed 3DS invoice? Does the invoice still remain open or will it eventually become uncollectible if I specify it in the settings? I imagine customers will be displeased if they have an open invoice / outstanding balance that was failed right after they just successfully paid one.
Well, that's a completely different question, as that scenario does not involve a one-off Invoice.
In the scenario you describe there would be two completely separate Subscriptions that would have no impact on each other. You should avoid creating multiple Subscriptions for your customers if you only want one.
Backing up a bit, can you tell me what you're trying to build so I can make a recommendation for how to proceed?
ok i am wondering how i could prevent that and how to do it via the api
basically that was an undesirable thing i found while testing
but in terms of that settings page i am trying to see if i can make some webhooks that do similar things but for everything like one time payments
for the scenario i just described it would be a normal checkout flow of buying a sub on my site
At a high level my recommendation would be to write some code that detects if they have a Subscription or not (in any state), and if they do direct them to the Customer Portal to manage that Subscription: https://stripe.com/docs/customer-management/get-started
Otherwise you show them the link to create a Subscription.