#tx_monster

1 messages · Page 1 of 1 (latest)

hybrid galeBOT
odd karma
#

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

hallow thorn
#

If the invoices stay there opened, is there any possibility that they are automatically billed to the customer?

hybrid galeBOT
hallow thorn
#

And, can you confirm that there is no field like void_at for invoices in order to plan their void?

#

(like an expiration)

tepid moon
#

👋 taking over for my colleague. Let me catch up.

tepid moon
#

sorry for the delay

hallow thorn
#

NP

tepid moon
#

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 the latest_invoice.payment_intent which will be null, you need to use pending_setup_intent

hallow thorn
#

Yes, that's what we do

tepid moon
#

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

hallow thorn
#

What is that?

tepid moon
#

the only difference in your case would be creating the Invoice/Subscription instead of creating a PaymentIntent

hallow thorn
#

After the payment intent confirmation, do stripe create an invoice?

tepid moon
#

no

#

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

hallow thorn
#

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?

tepid moon
#

exactly

#

actually while confirming not before

hallow thorn
#

Ok, last question: is there any way to plan the void date of a invoice (like cancel_at for subscriptions?)

tepid moon
#

not really

hallow thorn
#

Sorry: not really or not at all?

tepid moon
#

I'm not sure what's the difference

#

if you want a simpler answer: no

hallow thorn
#

Ok, thankyou for your precious help

#

Have a nice day!