Lunar

[earnest seal]

👋 Hi there, Happy to help!
Yes of course, what is your question ?

[wooden cargo]

I'm testing with various cards by JSing on the front end :

stripe.createPaymentMethod({
type: 'card',
card: cardElement
})

then returning the token to my backend (PHP) and creating + confirming a PaymentIntent in 1 step, tagging it as MOTO.

But If I put through this test card which requires authentication. I get the error that the card requires authentication.

I would have thought that MOTO circumvents that issue in the real world, no card to my knowledge can ONLY process 3d secure payments, they all are capable of card holder not present transactions.

So is this a test server situation, where that card will always give that error.

Or is there a flaw in my processing of the card which could mean a real world card declines because it needs 3D secure, even though it's MOTO ?

[earnest seal]

To test the behavior where MOTO transactions are not exempted from SCA by the cardholder’s bank, use the pm_card_authenticationRequired test card as a paymentMethod Id

[wooden cargo]

So in the real world, there are cards which will fail because 3DS is required by card issuer - despite the transaction being MOTO ?

I've never come across one of those.