EU VAT number check fails every time

[Scarface09]

Hi,

I'm trying to get the EU VAT feature working in the Commerce application, but the VAT number check fails every single time, even though the VAT numbers I tested are valid according to the official VIES VAT check.

Is there something else I need to set up, or is this a bug? I'm using the latest version of Invision.

[Jim M]

There was a bug we noticed with the vendor we used to check VAT numbers with which brought false positives. If you are able to provide an example VAT in a message to me, I can verify if it is impacted.

[Marc]

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

[Stuart Silvester]

The EU VAT service updated their API. I sent them an email a few weeks ago and received a response on Thursday. We've made the required changes which should be in the next monthly release.

[opentype]

I always wonder how you decide what ends up being a patch and what is added to some future updates. 

Clients abandoning a purchase because the sign-up form is faulty seems a crucial bug to me and I would rather expect it to be something that needs fixing as soon as possible. After all, this can cost us money and clients. 

In the same spirit, I would have expected this significant visual bug to be a quick patch and that didn’t even make it in the release that followed the acknowledgement of the bug. I have this problem now across multiple websites since July with thousands of visitors accessing these faulty pages and so far I don’t even know if it will be in the next monthly release. 

 

 

Edited September 25, 2022 by opentype

[Marc]

Usually, an issue on the software that is affecting a large number of users is something that would be patched. i can certainly flag this one up though so it can be looked at.

With regard the carousel one, that bug has not yet been addressed, so could not be released as fixed. 

[Marc]

@opentype We are going to get this one patched for you. Please bear with us