|
oohar
|
December 25, 2024 at 2:18 pm
I am running an EE3 installation that offers many free event registrations. We occasionally sell event tickets at specific prices. PayPal STANDARD has been running these transactions since 2012.
I see the January 15th notice that PayPal Standard is being deprecated. I read the pages linked to the conversion process. I fear that it was written for EE4 or EE5 users. It does not seem to match the available options inside my EE3 Payment Setting options.
What should I be doing regarding this notice for EE3?
In my EE3 payment section, I see the existing PayPal STANDARD and PayPal PRO (both stated to be disappearing). The notice says both will be deprecated and that “PayPal COMMERCE” should be selected, but I do not see PayPal COMMERCE in the options list.
I could not find anything specific to those of us who are still running the older versions.
|
|
Tony
|
December 30, 2024 at 7:30 am
Hi there,
The payment method deprecation notice applies to EE4+ only and EE3 will not change on Jan 15th.
The system we use for plugin updates/notices doesn’t differentiate between versions and simply pushes the notice out to any version of EE that checks our update server for updates (just to explain why you’ve seen that message on EE3).
—
A couple of notes here (for OP and any future readers of this thread).
PayPal Standard/Express/Pro are considered to be deprecated by PayPal themselves in favour of PayPal Commerce. We deprecated PayPal Standard a long time ago due to how unreliable it can be and it hasn’t loaded for new installs of EE4 since doing so (it still loads for users who are already using it, just not new). Since PayPal has deprecated the legacy integrations in favour of PayPal Commerce, we have deprecated those versions to follow suit. In doing so, we officially deprecated our payment methods using those legacy integrations (hence the notice).
Why have we done this? Becuase PayPal Commerce is the ‘latest’ integration PayPal provide, you don’t need a specific PayPal account to use it and it supports both the ‘Express buttons’ (the PayPal pay buttons) and ‘onsite card payment fields’ (which actually load from PayPal servers) in a way that reduces your PCI Compliance. It also means we only need to support a single payment method in place of the 3/4 it replaces, which means we focus on a single integration method and can add new features to it, fix bugs quicker in that single integration rather than working on legacy integrations (so yes, some of that also ‘helps’ us with support, but not by much).
—
To @oohar, as you’re using EE3 I think it’s important to note here that EE3 is (and again has been for a while) considered our legacy product. Whilst we still provide support for it and help with issues that come up with it from time to time, we are not actively developing EE3 further and all future development will be done on EE4.
Eventually, EE3 will be officially deprecated in favour of EE4. We built migration scripts into EE4 so that moving from EE3 to EE4 moves over as much data as we can, so having said that I would recommend setting aside some time to plan a move from EE3 -> EE4 within 2025 (we can help with this if needed, but migrations and issues around those which aren’t an issue with EE itself aren’t covered under our support licenses so would be an additional charge which we would discuss first).
|
|
oohar
|
December 30, 2024 at 7:54 am
Thank you kindly for the explanation. I will budget an upgrade to the EE4 for my non-profit organization in 2025. With that change-over, I will probably also encourage our back-office people to light up the Quickbooks Merchant Panel, which QB Online is pushing upon businesses that have switched to QBO.
Happy New Year to everybody…
|
|
Tony
|
December 30, 2024 at 8:14 am
Ohhh, interesting.
We have an EE4 QuickBooks Integration but I’m not sure if it’ll work with a Merchant Panel if that’s something new… I’ll make a note to investigate this.
—
Happy New Year to everybody…
Thank you, and the same to you 🙂
|
