Hi @logancommunika,
I just tested the VAT ID, but the plugin was able to verify it. I can see in the “Validation & Progress” section, the “First validation method” is set to “Simple”. Could you please set it to “SOAP” and see if it works better for you?
Please let us know if the issue persists.
Kind regards,
Moshtafizur
I tested with all available methods but the result remains the same.
Hi @logancommunika,
In such a case, please go to the “Admin & Advanced” section of the plugin and enable the “Debug” option there. Then please try to verify the VAT ID on the checkout page again. Then please go to “WooCommerce > Status > Logs”, you will be able to see some error logs there. Please take a screenshot of the error logs and submit it here. It will help us understand the root issue.
Kind regards,
Moshtafizur
here are the mistakes : https://ibb.co/zFbchpf
Hi there,
Thanks for the screenshot.
I have escalated this with our development team. They will get back to you as soon as they can.
Kind regards,
Moshtafizur
Hi again,
I see the logs are showing CURL method, it might that when you tested other methods (mainly SOAP), there was a wrong setting which is verify VAT numbers without country code “Autoriser la saisie du numéro de TVA sans code de pays” unticked while trying to verify with a VAT number without BE in the beginning.
Please tick that option, change validation method to SOAP and then try again, I hope it solves it, if not, please provide logs screenshot.
Omar
Hello I applied the changes and repeated two tests one with “BE” and one without. Invalid both.
Here are the logs: https://postimg.cc/m1ssmzvC
Thanks, if you notice the last 4 lines in the logs, they indicate that the IP you’re using is blocked from VIES (VAT verification system), please check Q15 in this link for resolution (or contact your hosting) for resolution:
https://ec.europa.eu/taxation_customs/vies/#/faq
Please let us know if we can be in any further help.
Omar
I understand the problem related to my ip address but why do users of the site encounter the same problem then?
Unfortunately yes, since it’s related to the IP doing the verification, which is your website IP and not your own IP. I would assume if you try a similar plugin, it will give the same error