#Nars

1 messages · Page 1 of 1 (latest)

bold wadiBOT
burnt dust
thorny tiger
#

Okay how can I confirm the payment

#

With the payment token?

burnt dust
thorny tiger
#

Okay is there any risk to approach? the frontend now has the publishable key, client secret and the payment method ID which means someone could tamper the app and make a payment without the card owner's authorization

burnt dust
#

there's no added risk really beyond a normal payment. Having the publishable key and client secret lets anyone attempt an API call to make a payment

#

the main thing is you should only be providing a client_secret to the frontend when you have authenticated the user(i.e. they've logged into their customer account in your system or so on)

thorny tiger
#

Yes but in case of not displaying saved cards, the customer has to enter card details on their own

#

So they would be aware they are making a payment

#

Slightly concerned about user's consent in case of saved cards

#

Is there any way by which when I display the last 4 digits in the UI I can also ask for their CVC which can later be authenticated?

burnt dust
#

I mean if someone is running code on the user's browser without their consent they're already compromised

thorny tiger
#

Lol okay

burnt dust
thorny tiger
#

Got it will check this out

#

One more thing

#

Do other apps also follow this approach (without cvc auth) I mean is this the conventional approach to display saved cards?

burnt dust
#

yes