-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Credit Card Processing - Security code error handling failing. #726
Comments
For me it's working well: https://www.screencast.com/t/JLcx7FcEpuVT |
It seems other plugins conflict with our plugin, Can you please ask user to provide website URL for more troubleshoot? |
@kcppdevelopers maybe the form validation form #735 fixes this..?? |
I guess we'd still need to know why the JSON result was invalid. I'll ask them to provide info for us to test that. |
Responded to the user asking for direct access. |
Not sure if this is only related to security code field or any JSON result at all that would include an error, but this is how we can reproduce it.
Run a test for PayFlow, but enter an incorrect value for the security code. For example, just enter a single character instead of 3. What's happening is that we're getting an error back from PayPal because of the mis-matching CSC. The JSON result looks like this:
{"result":"failure","messages":"<ul class=\"woocommerce-error\">\n\t\t\t<li>Payment error: 114-CVV2 Mismatch: 15004-This transaction cannot be processed. Please enter a valid Credit Card Verification Number.<\/li>\n\t<\/ul>\n","refresh":false,"reload":false}
So the error from PayPal is 15004 - Please enter a valid Credit Card Verification Number, which is what should be getting displayed back on the screen instead of that weird JSON error. It looks like the error value in the JSON string is including some extra HTML junk, though, and that's causing the JSON string itself to be invalid.
We need to fix this in PayFlow and also check all the other gateways, too, to make sure the same thing isn't happening there.
The text was updated successfully, but these errors were encountered: