accepted payment logos

Also we have had a couple of orders recently fail with error code 2007. After speaking with sagepay support it turns out it is because of 3D secure registered cards. I cannot be sure if the redirect to enter password is not working properly, or if they are entering the wrong password there, or something else? I was told that it would be best to turn off 3D secure. Is there an existing setting which I can select to turn this off? Or is this another feature that can be implemented?

We have also just had a customer message us with expiry date in 2021 but this date is not available to select.

Thanks for you assistance,

Alessandro

3d secure you manage through sagepay’s admin screen.
I will look at adding additional years to next update.

Thanks

Steve

Thank you very much,

Alessandro

no problem

Hi,

if I can give an update on the 3D secure issue. We managed to remove the apply 3D secure in our sagepay admin section. However now it seems we are getting a number of orders coming through with the showing this error:

NOTAUTHED The Authorisation was Declined by the bank. (Code: 2000)

Speaking to sagepay they have said the bank are refusing payment because our site will not allow 3D secure. So if I was to enable 3D secure again is it a plugin issue we were having with the redirects not working properly for customers to enter their password?

Thanks,

Alessandro

Hi
Are you reproduce the problem, does it show ‘Please Wait’?

Is it intermittent, does it happen on specific types of cards or clients?

If there was a general issue with the plugin with 3DSecure I would have expected to see more tickets raised.

Regards

Steve

Hi,

I wouldn’t be able to reproduce the problem, as these are purchases used with cards that require 3D secure.

I do not know if this is an issue occurring with a particular card type etc as the only information I can see is the error message displayed below. We have also had a few more of these over the weekend, which is a concern.

NOTAUTHED The Authorisation was Declined by the bank. (Code: 2000)

Also are you able to tell me when the next update will be available as the postcode issue has also occurred quite a few times over the past week which is pending transactions.

Thanks,

Alessandro

We have also had a a few more expiry date issues. Needs to be updated to include 2021 and above.

Many thanks,

Alessandro

Hi,

any updates on the above?

Many thanks,

Alessandro

Hi,
1.7.4 should be release over the next few days, apologies for the delay.

I’ve extended the Card validation date to 12 years.
Added default currency option for multilingual sites.
Postcode support for non Postcode countries.

regards
Steve

Thanks, that will really help to solve some of the issues we are having.

Will there be any update for the error code (2000) regarding the 3D secure issue we have been having?

Thanks,

Alessandro

The 2000 error I’m unable to reproduce the problem, without more information it’s almost impossible. So any feedback from your clients would be appreciated – what device they are using, what credit/debit card they are using.

thanks

Steve

Thanks for the update, really appreciate it.

Although we have had an order come in this morning from Hong Kong which is still pending, and the error message is:

MALFORMED The BillingPostCode is required. (Code: 3090)

I have noticed that when selecting Hong Kong at the checkout the postcode field does appear, but it is not set as a required field, like it usually is for other locations. Does the latest plugin update not submit a dummy postcode in this case where a postcode could have been submitted by the user, but was left empty?

Thanks,

Alessandro

Also an order has come in now from Zimbabwe with the same postcode issue:

MALFORMED The BillingPostCode is required. (Code: 3090)

This is an area where postcode does not appear at all during checkout, I thought the latest update would have submitted the dummy postcode for this?

Thanks,

Alessandro

I’m using WooCommerce countries class to determine whether the postcode is required

With Hong Kong the postcode isn’t required but is visible as set by Woocommerce – I’m assuming (and would make sense that if it’s blank we should use the dummy code) – correct?

Zimbabwe isn’t listed as being different to default, so in Woocommerce it does require a postcode – this needs to raised with their developers, giving them the correct address format similar to the following: ‘ZW’ => “{name}\n{company}\n{address_1}\n{city}\n{country}” – I don’t know what the correct format would be.

regards

Steve