#discovering-stripe_api
pure magnetBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1254779260023996497
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
trail oracleBOT
rustic pagoda
Hi there 👋 can you elaborate on what you're referring to by "device gathering" here?
@jovial zephyr are you still around to tell me more about what you're asking about?
jovial zephyr
Yes, so we are working on Google pay integration using - 3ds Authenticaiton - MANUAL approach. I see the Challenge process step as per https://docs.stripe.com/payments/3d-secure/authentication-flow#manual-three-ds wondering how we need to handle device information without stripe.js as per https://support.stripe.com/questions/3d-secure-2-device-information
I mean sending the device information in the request without using Stripe libraries
rustic pagoda
I'm not aware of anything additional you need to do there. Are you encountering errors during your testing that are leading you to think otherwise?
jovial zephyr
We have some good few trial tests so far but they not able to trigger a request that requires us to send the device information as we normally do for other 3ds integration so wondering what we have missed
rustic pagoda
I'm sorry, I'm not sure what that means. Can you be more specific?
jovial zephyr
So, other payment providers, normally have a 2 step process to complete payment with 3ds. The terminology used for the first step differs from one to another. Common terms are Gather Device information or Identify Shopper or 3DSMethod. The second step is obviously the challenge.
With Stripe, The first step as given here https://support.stripe.com/questions/3d-secure-2-device-information seems to be done by the stripe.js. Is it possible for us to gather this info manually and send it
rustic pagoda
Not that I'm aware of, I've not heard of anything like that before. Let me double check with my teammates.
Ah ha, Radar Sessions are the feature I was forgetting about:
https://docs.stripe.com/radar/radar-session
long comet
to clarify, the device fingerprinting that 3DS requires is done by us even if you use the manual redirect(we run some Javascript during the redirect that does it), you don't have to do anything yourself(Radar Sessions mentioned above are separate from this 3DS-protocol-level thing if that's what you're specifically asking about). @jovial zephyr .