We currently have limited customer service staffing due to Coronavirus (COVID-19) safety precautions. We encourage you to find quick answers to your questions by searching the community forum, visiting our Help Center, or messaging us (message response times will be delayed). Thank you for your patience.
New to the community? Welcome! Please read our Community Rules and Guidelines
Thanks for continuing to chase this up for us - do you know whether the changes have now been pushed out to the Sandbox?
Apologies for the delayed response, I've been out of the office. I've checked in with our development team and they're working diligently to try and get this change into sandbox. It is unfortunately not completed yet, but the team hopes to have it done soon.
Another change is that this will not go into production, as previously stated, on March 15th. We are going to communicate this change again directly to merchants and anticipate the new date for this change to happen at the end of April.
Thank you for continuing to be patient with us while we work through this change. I will advise as soon as I hear this has been updated in the sandbox environment.
Hi @mikewz - the team has informed me that the changes are now in sandbox. Can you please test and let me know if you have any questions/concerns.
Why does PayPal have to change something (i.e. break it) that was working fine? modify=2 was working fine, and suddenly you just kill it off, for no real reason.
The new API is unnecessarily complex, and a major departure from the old one. No way to rework existing methods, so it pretty much requires a rewrite of the payment system.
I bet a lot of people will be looking at Stripe, which is easier to use, with better support, and considerably cheaper too.
I apologize for the inconvenience that this has caused and I can understand your frustration. We are currently working diligently to provide a better solution.