#GiovanniV - 3ds

1 messages · Page 1 of 1 (latest)

tacit chasm
#

As far as I know there is no general timeout rule/limit for card authentication in this context. Individual customer bank flows might have their own limitations on completing the authentication steps, but from Stripe's perspective those can complete several minutes later as needed.

winter crown
#

OK 1 more question : secret key never expires?. In that case if the timeout period is over, will customers be able to use the same client_secret later and complete the transaction?

tacit chasm
#

The PI client secret is static, it doesn't change

winter crown
#

Ok is there error code only related 3DS transaction processing.? if so can you point me to those

tacit chasm
winter crown
#

1 more my friend and thank you for your help

#

this integration also support recurring donations wherein CVC is not passed in subsequent transactions. How do we indicate such transactions so that these are exempted from the SCA flow (as this is the card not present scenario)?
We have experienced transaction declines when connecting to other payment gateways like MPGS, Adyen when passing MOTO transactions. How do you handle this on your end to ensure less declines?

tacit chasm
winter crown
#

OK thanks

#

How do you link previously authenticated transactions? One of the donation types that we support, i.e. monthly donations, makes a real-time request for the first transaction (assuming this is SCA authenticated) & then for subsequent monthly transactions, it’s the card not present scenario (MOTO). How do you understand these transactions are previously SCA authenticated or is this even required to be known?

tacit chasm
#

Those reucrring payments don't sound like moto (that's specifically for collected over phone/mail) -- but this is tracked and managed by Stripe system after you collect the payment details

winter crown
#

Ok you are the best thank you!