: Is it good idea to put a captcha on credit card payment form Is it good idea to put a captcha on credit card payment form? I am thinking to put one on my asp.net mvc application's payment

@Shelton105

i might be wrong but Captcha is used to disable spamming/automating input so that the user would have to do it his/herself.

You could probably just create a delay so that the user can't submit details repeatedly in a short amount of time instead of adding another field to fill out.

Vote Up Vote Down

@Kristi941

Your goal is to make the payment process as simple and straightforward as possible. Adding a CAPTCHA to your payment form will do the opposite of that.

CAPTCHAs are notoriously difficult to complete. They have to be complex to defeat bots that are continually getting more and more sophisticated. But that complexity makes it more difficult for humans to complete as well. If you make the CAPTCHA easy to complete then not only is it easier for the bots to defeat, all you've done is add yet another field for users to fill out.

Using session tokens and honeypots are easy ways to find bots without humans ever knowing they were there. So start of with them and then if a user seems to be submitting a lot of forms in a short period of time and/or their payments are repeatedly declined, then use a CAPTCHA to make sure they are a human being.

Vote Up Vote Down

@Turnbaugh106

I'm not the biggest fan of captcha's but when they are useful they should be used.

If you validate card number (as I think you should) you could use a captcha only after a certain number of wrong successive tries by a user (identified by its IP address and timestamp).

Vote Up Vote Down