#Morio
hasty dawn
ok in that case what you can do is create the subscription
give a trial for the 2 months
winged fractal
But the problem I have is that the following screen from the documentation shows that it is free
hasty dawn
and on the third month you can update the subscription and add some add_invoice_items https://stripe.com/docs/api/subscriptions/update#update_subscription-add_invoice_items
winged fractal
Is it possible to modify the default screen of the trial period somehow ?
Because in our scenario it would be misleading telling the customer that it is free
Because we invoice them afterwards
winged fractal
Thank you ! 🙂
hasty dawn
you'd have to change the integration
winged fractal
Do you know (couldn't find it in the api) if the following is possible:
Customer starts a subscription with first of april
but the first subscription invoice comes with first of june ?
Without using the trial options
So delaying the billing cycle with a checkout session ?
@hasty dawn ?
winged fractal
thanks
winged fractal
So from a technical point would this workflow work:
- User selectes a subscription type
- We create a customer object + a subscription object
-- The subscription object billing start cycle is in the future - We create a checkout session for this customer + the created subscription
winged fractal
But we can't set pause collection when creating the subscription
We can't create the subscription with pause_collection with the checkout session
And imho we would like to create the subscription but on creation we want to already pause it for e.g. 2 months
hasty dawn
let me check if there's a way with Checkout
clever mothBOT
jaunty wing
Hi! I'm taking over this thread.
winged fractal
Thank you very much!
jaunty wing
Your use case is quite complex, so I don't think it can work with a Checkout Session (unless you use a free trial for the first two months, but then the wording on the Checkout Session may be confusing)
Instead I would recommend to build a custom integration with Subscription Schedules + Payment Element https://stripe.com/docs/billing/subscriptions/subscription-schedules
This would allow you to create a subscription with 2 month free (first phrase), and then start the invoice the user
winged fractal
Thank you soma we will look into it !
One last question @jaunty wing
Would the following be possible (seems like the easiest way):
- Customer selects a subscription (we store the subscription type in one of our systems - this does not do anything it is just for later setup of the subscription in stripe)
- We collect the user payment credentials via a setupindent
- As soon as we are ready to activate the stripe subscription process we just create the subscription via an api call using the payment credentials we collected with the setupindent?
jaunty wing
Sorry for the delay (Discord is busy). Yes that should work!
Note that there's always the risk that the first payment of the Subscription will require 3DS. In this case you will need to ask the user to come back to your website/app to go though the 3DS flow with https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-attached
winged fractal
Ok thanks for pointing that out
smoky otter
Hi @jaunty wing, I'm working with @winged fractal on this. You said it would work for us to track the user's subscription option and just take the setupintent up front to get the payment method.
- Would that work if we decided to start billing the customer 2 months later, using stripe subscriptions, where we collect for those previous 2 months in arrears?
Essentially creating a new subscription in Stripe, but taking payment as if it started 2 months ago
jaunty wing
Yes with a SetupIntent you get a PaymentMethod. And then you can reuse that PaymentMEthod for whatever you need (one time payment, subscription, etc.)
But keep in mind that the actually payment could fail, for example if the card was lost/stolen/expired in the meantime, if there are not enough funds on the card, or if 3DS is required (as explained just above).
smoky otter
Great, thanks. Would that mean we'd be making charges independent of the subscription object? I'm guessing a can't create a Stripe subscription today and take a payment for February 2023 on that new Subscription object?
jaunty wing
Would that mean we'd be making charges independent of the subscription object?
That's up to you. When you create the subscription you could add aninvoice_itemand it will be added to the first invoice of the subscription
https://stripe.com/docs/api/subscriptions/create#create_subscription-add_invoice_items
hasty dawn
👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!
smoky otter
@hasty dawn Would the example above of adding invoice_items to the first subscription payment work for more complex subscriptions with multiple products?
For example, we will have a subscription based on use that for each month would contain X amount of product 1 and X amount of product 2.
If we create a subscription and add invoice items for the previous 2 months would the receipt it produced let us break down those previous items? Showing "X items for April at X price, X items for May at X price, X items for this month at X price (and ongoing for the next period)"
hasty dawn
you can add up to 20 items