#Talon-paymentintent

1 messages · Page 1 of 1 (latest)

fresh ermine
#

@distant forge you attempted to charge the card and 3D Secure was required on the payment.

#

I assume you want to test the case of that not being required on an off-session payment?

#

the other test cards(like 3184 one you used) just always require 3DS

distant forge
#

why payment intent creation is attempting to charge a client?

#

we want to handle 3D, How can I create an payment Intent and send payment intent ID to frontend if 3d is require

#

should I catch error and then update payment intent to on-session?

fresh ermine
#

why payment intent creation is attempting to charge a client?
that's what PaymentIntents are for
and you passed confirm:true which specifically means, try to charge now.

distant forge
#

so if i receive such error Do i need to update the payment intent or i should simply send payment intent ID to front end.
So front end can use this payment intent Id for 3ds

fresh ermine
#

~depends on the exact error!~

distant forge
fresh ermine
#

yeah sorry I misread the question

#

i should simply send payment intent ID to front end.
that's what you do yes

#

the link I posted describes it in detail

distant forge
#

no need to change offsession = false I guess

#

thank you