eWAY Payment Gateway v4.2.1 has just been released. This release includes changes that may resolve some card payment failures that confuse customers.

Card number validation

Card numbers are now given some basic validation in the web browser, before an eWAY transaction is attempted. Basic card number keying errors are now caught and the customer asked to check the number before trying again. This is done using JavaScript in the web browser because the card number is encrypted before being sent to the web server and eWAY.

Fix for duplicate card details

When other checkout fields cause validation errors, like missing address fields, a bug in previous versions caused the encrypted card number and security code to be added multiple times to the checkout. If the customer changed which card they wanted to use on their second attempt, the first card would be billed instead. This is now fixed.

Encrypted field masks

When the card number and security code are encrypted by eWAY’s Client Side Encryption, the original fields are wiped blank. That can be disconcerting for customers, so now a mask of bullet points is added to those fields (using a placeholder) so that it doesn’t look like the purchase is happening without a card number.

You can update to the latest version from your WordPress plugin admin page. Here’s the full changelog for eWAY Payment Gateway.