#moistcode-testing-3ds2
1 messages · Page 1 of 1 (latest)
Yup! I didn't know if it was okay to post it.
pi_3Kv80HFOrEmR4dyh1GhjuNrT this is the initial successful one.
pi_3Kv81lFOrEmR4dyh0IWMpivb this is the one after which was unsuccessful.
Also these are in testing environments.
Not if it is worth noting but I'm using the testing card provided by stripe (4000000000003220) under 3DS2 Required in https://stripe.com/docs/testing
Looking now!
No rush 🙂
Ah, the 3220 card requires 3DS on all transactions, no matter what - if you want to test a card that can be set up for future usage you'll want one of the ones here (https://stripe.com/docs/testing#authentication-and-setup)
Oooh I didn’t know there were some cases where 3ds is always required.
If that’s the case, I should probably send users an email or something.
When you set up a card for future usage we request an exemption for future charges, but it's always possible that the bank decides to reject the request and still ask for authentication
Gotcha. Do you know if all 3DS2 always require authentication or is it always up to the bank.
Gut tells me it’s up to banks.
3DS2 doesn't always require authentication (it just happens that our test cards behave that way) - for the most part it would be up to the banks
Gotcha, thanks again as always Karbi!