Payment Hack Security Feature

Payment Hack Security Feature

As we all know, there are attempts made on the merchant world every day, many from hackers trying to use online stores as a testing ground for valid credit card numbers.

The OpenUI™ helps you take steps to cut down such attempts by implementing timing scenarios for failed credit card attempts.

To access the feature:

In the admin menu, click the

next to Stores.

Click on Your Store's Link.

In the right-hand menu, click the OpenUI Security link.

Here, you can set specific timing effects on those inputting payments into the store for an order.

For example, if a customer shops the store and proceeds to checkout, and gets a decline on the credit card, it could be a bad card, a mistake on the input, or, possibly, a stolen card being tested by a hacker.

Level 1

This is the initial level and represents the customer's first attempts to make payment. Forcing the customer to wait 15 seconds before making another attempt is enough time to irritate a hacker, but short enough not to cause a customer much frustration.

Level 2

After X amount of attempts (by default this is 3), you can force the shopper to wait a longer period between attempts.

You can set the levels as you wish, just keep in mind that you don't want to frustrate legitimate customers so consider any human errors that can be made.

Payment Error Message
This message will be displayed on the screen if the consecutive payment attempts are failing. It will be displayed whenever the shopper is at the Level where the wait time is more than 30 seconds. You can customize this message and also use tokens.