#bernard.eugine

1 messages · Page 1 of 1 (latest)

tall terraceBOT
marble rose
#

👋 happy to help

#

unfortunately 3DS2 implementation is only available in the front-end so that the customer can authenticate the payment

summer path
#

Got it. If we collect the device_information ourselves, we wouldn't still be able to pass them to Stripe?

marble rose
summer path
#

Is there any API parameter within paymentsintent/confirm that can take the device_information parameter?

marble rose
#

if you don't want to use the PaymentElement in the first place to collect the payment details

summer path
marble rose
#

do you mind me asking how are you collecting the PaymentMethod in the first place?

summer path
#

We are PCI Compliant ourselves and we would collect the customer details using our own payment form and we would be integrating to Stripe only for payment processing through API_only integration

#

That is why, we wanted to see how we could pass the device_information to Stripe API endpoints to enable 3DS 2.0

#

For Adyen, we were able to integrate and do this by directly including 'browser_info' attribute in their /payments API Request

fast ether
#

Depends what you're looking for really. We support processing 3D Secure outside of Stripe and passing the results into Stripe for just acquiring but it's not public, you should talk to your sales contacts or https://support.stripe.com/?contact=true

If that's not what you mean and you just want to accept the raw PAN and use Stripe for processing 3DS and acquiring then you would just use the normal integration with PaymentIntents and raw PANs, you redirect the customer to the URL we provide for 3DS (https://stripe.com/docs/payments/3d-secure?platform=web#manual-redirect). That page will collect the information needed for 3DSv2 as an intersitial step before moving to the bank interface

summer path
#

Got it. So, the redirect url will be the one that collects the device information and not the Stripe Elements?

fast ether
#

yes

summer path
#

So, if the device information is only collected after we redirect the customer to URL, how does Stripe handle cases where the network deems the device_information to be sufficient enough and recommends to skip the user authentication/OTP verification step?

fast ether
#

it just redirects straight to to return_url

summer path
#

Got it. Thanks @fast ether!