Open wmortada opened 5 years ago
Hi @wmortada!
We're also interested in understanding the implications here, whether any changes need to be made. Have you received any confirmation elsewhere?
Hi both - this extension does use the Server integration, which shouldn't require any changes:
Server integration – There will be no mandatory changes to your current integration. We will undertake some proactive steps in the coming weeks to ensure you are ready.
.. according to https://www.sagepay.co.uk/support/16/3d-secure-v2-what-do-customers-need-to-do
However, you may want to also consider the nz.co.fuzion.omnipaymultiprocessor extension for this, which has some good integration for Sagepay, as I understand it - and is probably a bit better maintained.
As far as I'm aware, Circle are no longer actively maintaining this.
Thanks both. I haven't found out any more than what I posted above. It does indeed look like this extension is no longer being actively maintained. I'm looking at the feasibility of moving to Matt's fork of the Omnipay extension which seems to be the most up-to-date: https://civicrm.org/extensions/sagepay-omnipay-version
SagePay are contacting customers to alert them to the new EU Payment Services Directive (PSD2) that comes into effect on 14 September 2019. A key element of this directive is the introduction of 2-factor authentication for online transactions processed in the EEA, via 3D Secure or 3D Secure v2.
SagePay are asking customers to take action now to prepare for this change as follows:
I have looked into this myself and it looks like this extension uses the server integration and I believe that this means that no changes are required.
Could someone else please take a look at this to confirm?