#jaunt-subscriptions
velvet crypt
Hi, yes: sub_1KGpE1Aas9MbjlbveWHPlD4Z
trail mica
Gotcha - so Subscriptions with status: incomplete will stay incomplete unless payment on the first invoice has been made (it will not be attempted through an automatic retry). If payment hasn't been made after 23 hours the subscription will automatically transition to incomplete_expired and will be considered expired/cancelled so you dn't need to worry about them
trail mica
Where specifically do you let the users see their invoices? In your own UI that you've built?
velvet crypt
Yes exactly.
Maybe I only need to show reciepts?
I thought that subscriptions didn't used to show up under receipts, but now they do.
trail mica
I believe when the subscription has been expired it will void the underlying invoices - you can limit your UI to only show non-voided invoices
velvet crypt
So they would see both invoices (the failed and successful one) for 23 hours?
The invoices look the same by the way.
It might be the only time they actually look at the invoices.
I guess I could only download "paid" invoices for customers.
But I guess that could be confusing for alternate payment methods out there.
trail mica
Let's back up for a second here - what is your goal in the UI? To show the customer all of their already paid invoices?
velvet crypt
Good question. Originally (starting a year or so ago), I think we added invoice view because subscriptions didn't seem to show up as receipts. But now that they do, I'm not sure what the benefit is. Unless a failed invoice had a link that helped the customer pay it I guess, but does that ever happen? Maybe there is no purpose for my invoice view.
trail mica
If your goal is just to show invoices in lieu or receipts, then you can limit your UI to just show the Invoices that have a status of paid so that the never see the ones that are still open.
velvet crypt
Since I show receipts as well, I guess there's no point. Is there any other good reason to show invoices for checkout subscriptions?
trail mica
That's really up to you and your integration
velvet crypt
Ok. Was just wondering about common practices.
trail mica
Yeah it really depends - some users may want to show their customers all their unpaid invoice
velvet crypt
I see. Yes things are different if this is several months down the road of a subscription. I really wish a subscription wasn't created until the first successful payment, but I guess there's a good reason?
And why a new subscription is created when trying to subscribe to the same price/product. Instead of just converting the other one to success.
trail mica
I really wish a subscription wasn't created until the first successful payment, but I guess there's a good reason?
Yeah, a big reason for this is because Subscriptions are built on top of Invoices and Payment Intents. In order to attempt payment we need the Payment Intent to be created first (hence why we need the Subscription to be created)
velvet crypt
I see. Ok, well thanks for the help, much appreciated.
I can probably find a good work-around with this info.
trail mica
👍 glad it was helpful!