#JosePersichini

1 messages · Page 1 of 1 (latest)

wet zincBOT
terse onyx
#

Hi there

#

This mostly depends on the integration you are using.

#

Are you following a particular guide?

reef nebula
#

Yes

#

I'm creating a ClientSecret on backend (.NET) and a <PaymentElement> on frontend (react)

#

With setup intents

terse onyx
#

Ah okay so you are saving payment methods to take payment at a later date?

reef nebula
#

Exactly

terse onyx
#

Then you can see info like last4 + expiration

#

You won't have access to stuff like the full PAN or the CVC as that is sensitive info that we handle for you.

reef nebula
#

Yes, I know

#

I don't want to store the PAN and the CVV

#

I just only want to tell Stripe to validate that data during the payment method creation

#

I was using what you said

#

But (in live mode) if I try to create a payment method filling the data with a valid CC number + an invalid CVV + an invalid exp date Stripe saves the Payment Method

terse onyx
#

If you are using a SetupIntent then we already performed the validation

reef nebula
#

No, I made a lot of tries

#

Entering wrong data

terse onyx
#

Sure so a couple things here.

reef nebula
#

And Stripe is saving the Payment Methods without any problem

terse onyx
#

First, it is up to the issuer whether they care about this "incorrect data". We generally perform a card authorization with the issuer when you confirm a SetupIntent and then the issuer tells us whether it is valid or whether they decline this authorization. We just pass along that result to you.

reef nebula
#

Ok, I see

#

So there is no way to check if the CC information is valid on EVERY creation of a payment method right?

terse onyx
#

Correct.

reef nebula
#

Ok

#

So thanks!