#GiovanniV-publishablekey-elements

1 messages · Page 1 of 1 (latest)

half flicker
calm nest
#

Hello! Yes you do need to provide the publishable key to use Elements (or event Stripe.js in general). That key is safe to disseminate publically. It is okay and expected for it to be sent to the client as plain text.

light crest
#

ok thank you!

#

1 more question : After a successful 3DS authentication can we pass the authentication result to the Payment Intent API and is this possible via backend API? Please confirm the parameters/fields?

calm nest
#

Stripe will automatically get the results of the 3DS auth. Can you tell me a bit more about the 3DS scenario that you are trying to handle now?

light crest
#

is standard 1 time transaction validation customer credit card for a charge

calm nest
#

Which flow are you using? We should automatically get the results and advance the process that you are using.

#

So with a PaymentIntent, we will confirm it once the user has authorized. With a SetupIntent, we allow you to use the PaymentMethod that it creates for payment after the user completed 3DS auth.

#

You don't need to manually send us anything about the user completing 3DS auth. Are you running in to some kind of error at the moment?

light crest
#

ok I see all is manage after that inside the 3d secure method

#

thanks

#

1 more : How are callback functions handled using Stripe.js?

calm nest
#

What callback are you looking for here?

light crest
#

is via webhooks I found the way thank you

calm nest
#

Yes, glad you found that. Any other questions on webhooks at the moment?

light crest
#

1 more : Is there any flow or sample reference code to handle SCA Authentication using Stripe.js?

light crest
#

?

urban laurel
#

Hello! Pretty much all of our current guides show SCA-compatible payment flows unless they note otherwise.

light crest
#

ok thank you!