edi - requires_action | Stripe Developers | Page 1

hearty quartz Apr 12, 2022, 9:14 PM

#

celest moss Apr 12, 2022, 9:15 PM

#

Hi there 🙂

hearty quartz Apr 12, 2022, 9:15 PM

#

Hi there! Can you elaborate a bit?

celest moss Apr 12, 2022, 9:15 PM

#

Yeah, was waiting for you to create the thread first

#

I think it's fine if I attache the timeline directly?

#

pi_3KnjmDFEYYjHn8Dy01voGyTo

#

Basically, we have a scooter rental company

#

And when customers try to ride via "pay as you go", we will charge an initial 3 euros (30 nok)

#

Since you are "on session" we don't set it to false, because it might require 3DS, as you can see via my initial request

#

I'm thinking I'm doing something wrong, because, for quite a few some customers, it seems like we fail the 3ds verification

#

But basically, I send the request which creates the payment intent, as you can see

#

That's properly sorted

#

The status is then set for some people to "require_action" which, as we know, basically means 3DS verification is needed, as per stripe's docs

#

Since the customer is NOT off session, I take the client secret and pass it back to the customer's phone (react native app), in order to "verify" it via 3DS

#

I use that payment intent's client secret, to try and confirm the payment, via the useConfirmSetupIntent hook in RN https://stripe.dev/stripe-react-native/api-reference/index.html#confirmSetupIntent

@stripe/stripe-react-native

Documentation for @stripe/stripe-react-native

#

As you can see here, that properly happens on the client's side, but for some reason, the status is still "requires_action" ... ?

#

So, I'm really not sure what I'm doing wrong ...

I create the payment intent with off session false.
I check if it requires any 3DS verification via "requires_action" status
If it does, I return the secret to the client, and there I trigger useConfirmPayment with that intent's secret

And then .. the payment is still requires_action ?

hearty quartz Apr 12, 2022, 9:25 PM

#

For the payment intent you supplied, it looks like it just failed 3DS, so the payment intent remaining int requires_action is expected behavior. Does that similar behavior appear for all your customers that auth via 3DS? Or just some?

celest moss Apr 12, 2022, 9:28 PM

#

Just some, others are OK.

But there are quite a few and I am wondering if this is only because they simply fail 3DS (if so, like wtf, are there so many people failing to verify their cards?)

#

eg. is there any other reason for which these transactions go back to requires_action, aside customers simply failing to verify?

#edi - requires_action