The purpose of this document is to help you understand
and correct some common errors and problems
experienced with the Verified Merchant Seal.
The Web domains you configure in the Merchant Interface will allow Authorize.Net to successfully authenticate your site(s) when a customer clicks the seal image. By configuring Web domains properly you can avoid problems with the functionality of your Verified Merchant Seal. If you are experiencing problems with the seal on your site, check your Web domains configuration in the Merchant Interface first.
You need to configure BOTH of the following domain formats for each of your domains: www.yourdomain.com and yourdomain.com. You must also configure any additional domains and subdomains (subdomain.yourdomain.com) on which you plan to display the seal.
You do not need to configure each distinct URL on which you plan to display the seal. By listing root domains and subdomains, all related pages such as www.yourdomain.com/page.html or subdomain.yourdomain/page.html will also be verifiable.
Check the list below for additional information about the error or problem you are experiencing.
I configured my domain in the Merchant Interface, but when I click on the seal I get an "Unable to Verify Site" message.
Open your Web page that displays the Verified Merchant Seal. Verify that one of the domains you configured in the Merchant Interface matches the domain in the Web address bar exactly. If the URLs do not match, add the domain that appears in the Web address bar to your Verified Merchant Seal Domains List on the Verified Merchant Seal page.
Note: You should configure BOTH of the following domain formats for each domain on which you would like to display the seal: www.yourdomain.com and domain.com.
The domain shown in the "Unable to Verify Site" pop-up window does not match the domain I configured in the Merchant Interface.
There are a couple of reasons why this problem might occur:
After pasting the code into my Web page, the page takes a long time to load and the seal does not appear.
If you used Microsoft FrontPage to implement the seal code, verify that the code contains src="https://VERIFY.AUTHORIZE.NET/ anetseal/seal.js." FrontPage may add "file" in place of "//" when you save the Web page. Edit the code back to "//" and try again.