#abignalet-sca

1 messages · Page 1 of 1 (latest)

storm jackal
#

@opal jetty sure, how can I help?

opal jetty
#

Here is the log

#

Can you validate we are using the SCA compliant version of the api?

#

I think yes but your support cannot answer...

storm jackal
#

sure, seems like a correct and normal integration that supports SCA to me

opal jetty
#

In this state, what could block us to be SCA compliant?

storm jackal
#

nothing, there's no SCA issue I can see

#

why do you think you're not?

opal jetty
#

cuz we are receiving some 402 auth_required errors using apple_pay for some banks

storm jackal
#

sure but I don't think that's your fault or anything to do with your integration

opal jetty
#

Okay

storm jackal
#

that can happen

#

it "shouldn't" since using Apple Pay is supposed to count as a second factor of authentication for the purposes of SCA

#

so the customer shouldn't need to also do 3D Secure

#

but maybe the bank's system is broken and they don't respect that, or something else went wrong

opal jetty
#

I monitored the error, an stripe do not return enough to make a 3DS following the error (no redirect_to_url)

#

Thank you for explanations

#

We also assume a bank problem

storm jackal
#

like that example you gave is nothing to do with 3DS

#

the bank generically declined the payment, it wasn't a "authentication required" decline

opal jetty
#

Yes nothing related to 3DS

#

The thing is according on the doc, the first confirmPayment returns the errors, we do not have the require_action status

storm jackal
#

sure, that can happen if it's just a regular decline

#

any payment can decline, the fact the user authorised the payment in Apple Pay doesn't really change anything, the bank can still decline the payment when you go to charge the card details that came from the Apple Pay wallet

#

in that example yes it looks like the bank requiring 3D Secure after Apple Pay, which is unusual but as mentioned above, can happen sometimes

#

it's also unusual we didn't return the requires_action status you're right

#

I'd expect us to have, so that needs some investigation

#

you're probably already in contact with our support team about that