alessandrofoglia

Yes Hong Kong would require the dummy postcode to be sent if left blank.

Not sure what you mean for Zimbabwe? When I enter my address as Zimbabwe in Woocommerce no postcode field appears. Therefore the dummy postcode would need to be set here for this location.

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

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

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

Hi,

any updates on the above?

Many 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,

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

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

Thank you very much,

Alessandro

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

Thanks for sending over the file. I was going to attempt to test out the new updates you made, but I have just realised that our test site unfortunately is not synced with our sage pay account, and we also do not have SSL installed on our test site either, so I could not accurately test if the changes have worked.

We are now in a busy period taking regular orders online and I would not want to manually make any changes to this plugin that may disrupt this. However having this issue resolved is important to us. If you feel the plugin changes have been tested and are not causing any issues, please add this, I will be happy to update the plugin and will immediately test. Any issues and I will revert back the current version of the plugin.

Many thanks,

Alessandro

Thank you for the support. The modified file would be great. My email is [email protected].

Many thanks,

Alessandro

It seems that WooCommerce does not provide the field for a postcode in areas such as Vietnam and other locations where postcodes are not used. However for a payment to be accepted by SagePay it requires a value to be submitted for the postcode, which is the reason why our customers payments are not being accepted. I am struggling to figure out how I can find a solution to this issue as we need to be able to take payments to our SagePay account from all locations.

Would you know a way that we can potentially submit a dummy billing postcode within a transaction from a customer if one is not submitted due to their location? This way their payment can be accepted by SagePay.

I would really appreciate any assistance for this.

Thanks,

Alessandro

Our site is now live and taking payments. However we are discovering some payments appearing as cancelled. A potential customer based in Vietnam has reported the following error message:

MALFORMED – The BillingPostCode is required. (Code: 3090)

Is this a plugin issue?

Thanks,

Alessandro

thanks