#bananarino
uncut lotus
neon turret
Hello there
sharp moon
Hey!
neon turret
Do you have a request ID for the error you are seeing?
Or actually let's back up a second.
sharp moon
This one isn't popping up in my developer logs, but is just in my browser terminal
neon turret
I set the payment intent up so that it can be confirmed later on by the seller.
When you say that do you mean you want to be able to actually charge the PaymentMethod during a different page in your flow?
I assume you are using Payment Element here, yes?
sharp moon
Yeah, so the flow is that the customer puts in a "request", where they input their payment information with paymentElement. Then the seller is able to confirm, and charge their "request"
at a later time
Hey @neon turret just wanted to checkin again and see what you were thinking. I appreciate the help 🙏
sharp moon
You're totally fine, thank you!
neon turret
Okay so you have two options overall here
You could consider using Auth & Capture: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
That would involve authorizing immediately and then capturing once the seller "authorizes" the request.
The second option would be to use a SetupIntent here to set up the PaymentMehtod to be charged at the later time.
The only issue there is that the SetupIntent doesn't guarantee that the later charge will succeed.
So if that later charge fails, you have to bring the customer back on-session to collect a new PaymentMethod
sharp moon
Ok I getcha, I was also looking for clarification on what was happening before. So I was using confirmPayment() with elements as a parameter, and this was obviously saving the payment method of the customer. As a whole, I didn't want to confirm the payment there, I just wanted to save the paymentIntent in my DB. However since I'm not confirming, it no longer automatically saves the payment method to the payment intent. So my question is do you think there is a quick fix I can implement just to save the payment method and bring things back to the way they were?
neon turret
No not really. You can't use this flow if you aren't going to call confirmPayment() while Payment Element is rendered on the page.
sharp moon
Ok let me think for a sec
So its not possible for me to create a payment method with Elements, and then save that payment method to the payment intent?
neon turret
Sure it is. But you would use a SetupIntent like I said.
The SetupIntent would create the PaymentMethod
Then you would grab the PaymentMethod and use it with a PaymentIntent when ready to charge
sharp moon
The SetupIntent would create the PaymentMethod
ohhh I understand
neon turret
sharp moon
Ok thank you, I'm going to read this for a bit