#slurp-3ds2-radar
1 messages · Page 1 of 1 (latest)
Hey @young panther we don't know much about Radar here but I can try to help (easier to just ask the question next time)
hey sorry about that, so im just trying to learn more about radar and 3ds2 but it doesnt seem like there's a ton of documentation. the main thing im wondering about is what data i should be getting from customers at checkout in order to have a strong level of protection
our platform is still in beta but right now we're only collecting card number, exp, cvc, country and zip (it's a donation sort of platform so name and email are optional because we allow people to send anonymously) i'm just wondering if that's ok for having protection or what the sort of standards are for this
gotcha, that's what i figured but thought i might as well ask if there are any recommendations
thanks for taking thr time
sure thing!
if you use our PaymentElement you're all set we already collect information that is important
you can also pair this with the AddressElement to collect address details
understood. there's no physical products involved in our transactions so i think the address element might add too much friction
sounds good!
thanks again for explaining. have a great day!