#Celsian
1 messages · Page 1 of 1 (latest)
Hi there. Looking
Thank you.
Ah ok I see. Not sure off the top of my head if this is expected behavior
Let me look into this further
Thank you, if anyone is asking, I just want to create an incomplete subscription and only start it once payment information is received. (I'd rather not go the trial method as someone can just repeatedly start a checkout every day and get another 24 hour free trial)
I'd like to be able to apply a coupon code in the middle of that process and have it apply to the first invoice.
So in your example you updated the subscription with the coupon after the trial ended
I think you need to update the subscription with a coupon prior to the next invoice even being created for it to be automatically applied
Otherwise you have to update the draft invoice directly: https://stripe.com/docs/api/invoices/update#update_invoice-discounts
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Ok, that may work, let me give that shot.
Is there anyway to create an incomplete subscription without the invoice being finalized immediately?
I'd really rather not use the Trial mode for the reason stated above.
You could also use a subscription schedule as suggested by my colleague in that other thread
When the schedule starts, the subscription will be active but the first invoice will be in draft state, and you'll have ~1hr before it's automatically finalized.```
You'll have to update the draft invoice directly with the coupon in this scenario as well
That's fine, I can do that, the issue then becomes that the Subscription is started without a payment method, meaning that a user can just go to my checkout page, not enter any payment information, and be on a subscription for 24 hours before it auto cancels for lack of payment.
I figured that maybe I should be using payment intents instead, but I'm reading on your help docs that I cannot use coupons with payment intent.
I also thought of using SetupIntent, but that causes Google Pay and Apple Pay to show $0 when accepting card information.
Yeah no matter the route you have tradeoffs
So it's up to you
Setupintent could be good
Because then you could create subscription with coupon attached
Another option is you make the customer input a coupon prior to showing the PaymentElement and creating a Subscription
All up to you