#Austin_Rowe

1 messages · Page 1 of 1 (latest)

heady kilnBOT
sly wadi
#

Yeah if you create a payment intent with those two params, that will immediately try to confirm it and charge the user on whatever PaymentMethod you pass in

frail juniper
#

We use the payment intent in the payment elements for paying with non-saved payment methods on the frontend, so we need to maintain that functionality. So creating the intent with those fields isn't going to work for us.

Just need to be able to run something similar to stripe.confirmCardPayment and stripe.confirmBankAccountPayment server side... but it doesn't really seem to exist

#

Would it work to create with off_session: true but WITHOUT confirm: true that way when we're ready to run the charge we would just update the payment intent w/ confirm: true?

sly wadi
#

Or is there a reason that you don't want to do that call?

frail juniper
#

Hmm I think this might be what I need haha

#

Will it work with cards and us_bank_accounts?

#

Also connect w/ standard accounts?

sly wadi
#

Yep yep, both of those support offline payments

#

Or rather all four of them do

frail juniper
#

Ah, ok! Perfect! I guess when I call confirm I just need to ensure to pass in off_session: true, right?

sly wadi
#

Yes, if this is a scheduled payment and the user is not at their computer then off_session: true is appropriate

frail juniper
#

Also is there some way in the documentation to see which methods are frontend methods and which are server side? I had tried to use this method on the front end and tried to use the two methods I mentioned before server side. If I had known this one was server side and the other 2 were client side it could've sped up my process...

sly wadi
frail juniper
#

I see, thanks a ton @sly wadi ! You're worth your weight in gold 🙂

sly wadi
#

Dang I way a decent amount too