#mdubya
1 messages · Page 1 of 1 (latest)
using a card w/ 3D 'Always Authenticate'
Gotcha
Yeah this is pretty rare if you are setting up cards correctly
We will apply for the necessary exemptions so that 3DS is not triggered
However
An issuer can always require 3DS whenever they desire
So you should always be ready to bring your customer back on-session to complete 3DS if necessary
99% of my payments are off-session charges so if its requires "always" i'd just assume prohibit the card.
food for thought. that should be an option.
and then one other simple critique.
take req_yQ1rrfuOACViPo for example
the response message:
"This payment required an authentication action to complete, but error_on_requires_action was set. When you're ready, you can upgrade your integration to handle actions at https://stripe.com/docs/payments/payment-intents/upgrade-to-handle-actions."
right now my system shows the error message to the end user.
but the whole "When you're ready" non-sense should be in a seller message.
Yeah that's good feedback
I agree that part shouldn't be in the error message
99% of my payments are off-session charges so if its requires "always" i'd just assume prohibit the card.
Yeah that's not really how this works
The "always requires" is based upon on-session charges
We don't ever force 3DS for off_session