3.1 Credit Card Processing with PlugNPay / Firefox / Non-Encrypted Card Readers
Problem
3.1 Credit Card Processing with PlugNPay / Firefox / Non-Encrypted Card Readers
Encrypted Credit Card readers have reported an intermittent issue where some credit card swipes are read correctly by the reader but parsed incorrectly in the Firefox browser prior to transmission to PlugNPay. Upon receipt by PlugNPay, the transaction is refused due to unreadable data in the card fields.
For Example: When swiping a credit card, the non-encrypted card reader sees the name as 'John Smith,' but Firefox is sending 'J*/oh^n//S^m*ith' to PlugNPay, which is rejected as invalid.
Solution
Encrypted Credit Card readers have reported an intermittent issue where some credit card swipes are read correctly by the reader but parsed incorrectly in the Firefox browser prior to transmission to PlugNPay. Upon receipt by PlugNPay, the transaction is refused due to unreadable data in the card fields.
For Example: When swiping a credit card, the non-encrypted card reader sees the name as 'John Smith,' but Firefox is sending 'J*/oh^n//S^m*ith' to PlugNPay, which is rejected as invalid.
The issue is intermittent and has appeared in all Credit Card data entry fields, such as Name, Card Number, CVV, Address, etc...
VSI and PlugNPay have confirmed this is an issue with Firefox not consistently reading keyboard emulated card readers.
- We tested a number of different readers and had the same results.
- We tested on other websites and had the same results.
- It seems that Firefox reads the data correctly most of the time, but not all of the time.
- We tested with Chrome, and the data was consistently read correctly every time.
- We also tested swiping directly into Notepad and did not see the issue.
So unfortunately because this is an issue with Firefox that is not limited to RecTrac or Plug n Pay, there is nothing we'll be able to do on our end to fix it. Also, because we saw the same issue with multiple readers, we can't recommend a reader that will work consistently.
If you experience this issue, VSI's recommendation as of now is to use a different browser. We plan to research this further but do not know whether there will be a solution.