#mr.dude_18428

1 messages · Page 1 of 1 (latest)

meager sinewBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

true lance
#

Hi, let me help you with this.

#

Could you please share a bit more detail about your use case?

robust spruce
#

Hello
Yes, our workflow allows users to save CC, when the user is on the checkout screen he is presented with his saved CC, if the user wants to pay with the saved CC he needs to enter CVC code for that card, problem is that we are using paymentIntent API, and attaching CVC token is only possible if confirm:true , but the payment intent is already created before that moment

#

is there a way to always requrie CVC check

#

I mean, is there a way to decide when CVC check is required, meaning, there is a off_session workflow for when we dont need cvc, but any other case requries user to enter CVC code, and we dont want to relay on front-end validation only

true lance
#

You can confirm it on the frontend and provide the cvcElement:

stripe.confirmCardPayment(clientSecret, {
          payment_method: pm,
          payment_method_options: {
            card: {
              cvc: cvcElement,
            },
          }
        })
robust spruce
#

Yes, I'm aware of that code, but is that enough in terms of security? since in theory "malicious" user can remove the payment_menthod_option right?

#

Meaning, if there is only frontend validation, what about backend?

#

Can i config payment intent to require CVC recollection?

#

on the moment it is creaated

true lance
#

I understand, let me check.