Printable View
There is 3DS support. PayPal will send a 3DS request if it warrants it. That comes back through the webhook in the root.Quote:
Originally Posted by balihr
See this PayPal testing documentation for details: https://developer.paypal.com/api/res.../card-testing/
Cindy - Something appears to be happening right now, and I'm not sure if anyone else is experiencing this. 1.5.8a running the 1.0.5 version of the module.
I just noticed between last night and today that the module is disabled (after working fine).
I just enabled it again, and moved a pending (authorized only) order to a new ZenCart status (processing), and the module disabled again.
It gave this message: " The live credentials for the paypalr payment module are invalid. The payment module has been automatically disabled."
I logged into PayPal's Developer Portal and noticed that the setting was on Sandbox instead of LIVE (we didn't change this, so I don't know why it was on Sandbox mode).
I put it back to live mode, and made sure the credentials were correct in the module. But it keeps disabling. HELP!
EDIT - When I look in PayPal and edit the credentials to see the details, I see this:
Attachment 20912
Could that be the issue, and what would cause that?
Please use the curl tester at YOURDOMAIN.COM/extras/curltester.php to test over and over again to see if you get intermittent result on connection for "PayPal Express/Pro Server" and the "PayPal Express/Pro Sandbox"
It appears to be failing in some areas....see screenshot.Quote:
Originally Posted by barco57
Attachment 20917
Thanks Cindy. I've spent all day trying to get this to work, but whatever I do, PayPal always responds with 3ds_return, even when I cancel the transaction during 3DS verification. I give up in hope someone smarter than me (it's not like I've set the bar high...) sorts it out in the future.Quote:
Originally Posted by lat9
Based on what I can tell, 3DS is there, but not working. Since the module isn't checking for the 3DS response nor the EnrollmentStatus, Authentication_Status and LiabilityShift parameters at all, all transactions are authorized by default (speaking of 3DS only), meaning all liability falls down to the merchant. Please correct me if I'm wrong.
In case anyone else is having CURL Connection Issues to the PayPal REST server.......
The issue in our case was that the FIREWALL was blocking a list of countries that are high risk for hacking, fraud, and malicious behavior. It turns out that RUSSIA being in the CC_DENY list for our firewall was the issue.
Why? No idea. Russia (RU) has been in our ban list for over a year with no issue. But suddenly, as of February 19th, 2025, it appears that there is some kind of relationship between Paypal REST servers and Russia.
When we REMOVED the "RU" country from CC_DENY on our firewall, wallah! We could connect to the PayPal REST server. When we put RU back on the list, the connection couldn't be made.
Hopefully that can help someone else out there. Thanks to Cindy for helping to rule out all the other issues we thought it could be. <3
There are reports from several merchants that the intermittent issue happening earlier today and yesterday may be resolved.
Hopefully it has indeed been fixed. My last interaction with PayPal about it indicated that it was being escalated to a senior engineer to investigate.
v1.1.0 of the PayPal RESTful payment module is now available for download: https://www.zen-cart.com/downloads.php?do=file&id=2382
This release contains changes associated with the following GitHub issues:
#24: Display card payments' AVS/CVV status in the admin.
#48: Correct function signature.
#25: Add `Auth Only (Card Only)` transaction type.
#49: Add setting to enable `SCA_ALWAYS` on card payments and capture 3DS status from PayPal.
Is Update from 1.0.5 just a straight overwrite of the existing files? Or do I need to uninstall and reinstall?
Ignore me just found the read me. Simply overwrite the existing installation. Thanks