#tx_monster
1 messages · Page 1 of 1 (latest)
Hi! Let me help you with this.
Yes, that's fine. If that's too annoying to have opened Invoices and Subscriptions, you could instead collect the Payment Method first with SetupIntents and then create a Subscription/Invoice and charge them one go. Here's how you can create the Payment Method: https://stripe.com/docs/payments/save-and-reuse
If the invoices stay there opened, is there any possibility that they are automatically billed to the customer?
And, can you confirm that there is no field like void_at for invoices in order to plan their void?
(like an expiration)
👋 taking over for my colleague. Let me catch up.
sorry for the delay
NP
I'm going to go back to the first message you sent
I have a couple of things to address there
For Subscriptions, i first create a stripe subscription , then i fetch the related payment_intent and it's client secret, finally i send the intent to the client from which the user can confirm the intent by providing a payment method.
in the case of trials instead of using thelatest_invoice.payment_intentwhich will be null, you need to usepending_setup_intent
Yes, that's what we do
ok perfect just wanted to make sure that's the case
what you can do to improve your process is to use the deferred intent creation flow
What is that?
the only difference in your case would be creating the Invoice/Subscription instead of creating a PaymentIntent
After the payment intent confirmation, do stripe create an invoice?
no
you can implement the whole flow as shown in the doc I sent you, the only difference for you would be step 4 https://stripe.com/docs/payments/accept-a-payment-deferred?platform=web&type=payment#create-intent
in your case instead of creating a PaymentIntent you create an Invoice and send the Invoice's Payment Intent's client_secret to the front end
So the difference with my current implementation is that i would create the invoice and obtain the intent after the user inserts in stripe elements the PM information, and before confirming the intent, right?
Ok, last question: is there any way to plan the void date of a invoice (like cancel_at for subscriptions?)
not really
Sorry: not really or not at all?