#floppyrod-3DS

1 messages ยท Page 1 of 1 (latest)

acoustic blade
#

๐Ÿ‘‹ happy to help

woeful dragon
#

I think this is it "req_DD0KA0cFYJ1Zo7"

#

There are a few relating to this payment actually

#

I'll include the others too

#

req_fsuVYgFAYR3yun

#

req_T8FiPFFBphpTrk

#

req_VWqEMwKyz719Ha

acoustic blade
#

I'm taking a look

woeful dragon
#

thank you kind sir/ma'am/other

acoustic blade
#

for the first request req_DD0KA0cFYJ1Zo7 for pi_3L948nGHVipsFZDw0oC2bUg8 there was no next_action so no SCA needed

woeful dragon
#

but the payment method i used was one of the test cards that required SCA

#

or am I lost

acoustic blade
#

which card?

woeful dragon
#

4000000000003063

acoustic blade
#

oh sorry I just saw

#

it's in a different request

woeful dragon
#

yea we are creating the payment intent initially, and then attaching a payment method too it after

acoustic blade
#

how?

woeful dragon
acoustic blade
#

so you're not sending the client_secret to the Front-End and using it with Card or Payment Elements

#

right?

#

you're generating the PM on the front-end and sending it to your back-end

woeful dragon
#

our front end creates the PM and we send that ID to our backend which fires the Payment Intent Confirmation API and adds the PM ID to the request

acoustic blade
#

when you're creating the Payment Method is that what's causing the issue?

woeful dragon
#

Sorry Tarzan I have figured out the problem

#

We were accidentally making an additional request to the Payment Intent which was changing the status from "requires_source_action" to "requires_confirmation"

#

Apologies for wasting your time and thanks for your help as always ๐Ÿ˜‚