#kargoe
spark cradle
waxen hawk
Hello 👋
How can I help?
peak tree
Hi! We have a semi-complicated charge model/workflow. It does function and has functioned for a number of years. However, our Stripe rep thankfully just introduced me to the concept of 'continuous auth'. This, would streamline our model and flow and all in all make for a far better user experience.
Can you tell me, does continuous auth REQUIRE that the card be present and utilized in a card READER? Or, can the user merely input their card into the Stripe component in our native apps?
waxen hawk
Huh I've not heard of continuous authentication feature yet. Might be missing something here. Have they shared any docs with you regarding this?
peak tree
It's relatively new... I think just got out of beta. One sec, I'll find a link.
I've heard it described as both incremental and continuous - unsure which it actually is at this point.
However, it appears that this is only available for in-terminal transactions.
I'm trying to confirm that.
waxen hawk
Ah yes, I believe its only for Card Present transactions at the moment
peak tree
Bare with my ignorance of terms... 'Card present' == secondary hardware to check the card for chip/magnetic stripe/etc?
If 'card present' is true, then we know for fact that another piece of hardware has validated the card as 'being present'. Otherwise, all other transactions are just people entering their credit card number and it doesn't make TRUE the 'card present' value.
If that understanding is correct, does using the card-scan ability in Stripe Elements (use of the camera) allow for 'card present'?
waxen hawk
If that understanding is correct, does using the card-scan ability in Stripe Elements (use of the camera) allow for 'card present'?
Unfortunately, no. Card Present only qualifies for payments processed using a terminal reader
peak tree
Ok... I assumed that was what it was but thank you for your clarification.