cancel
Showing results for 
Search instead for 
Did you mean: 

javascript authorize.net verification

I need to put the verification seal javascript in an external file that my web editor does not change. I understand that FP and Expression Web change this, and the authorize.net fix is for me to go to the server and hand edit these files. First, there are way to many pages for this to be feasible. Second, the server that my client is on does not allow direct editing of the files anyway...  So what I need is to be able to put the verification javascript in an external file. Then I need the correct way to access this file so that authorize.net verifies this on the pages.

 

I have the js in an external file, but I have not been able to get authorize.net to work on any of the pages.

And yes, I have javascript enabled, have tried it in all browsers and it does not work.

No, the js file is not being altered when uploaded.

tcertain
Member
1 ACCEPTED SOLUTION

Accepted Solutions

tcertain,

 

It appears your web editor is modifying the html code copied from the merchant interface.  If you change 

 

src="//verify.authorize.net/anetseal/seal.js" 

 to

src="https://verify.authorize.net/anetseal/seal.js" 

 in your editor, it should correct the problem.

 

For more details, please see this support answer.

 

Richard

View solution in original post

6 REPLIES 6

You mean the merchant seal js file? I thought it run on the authorize.net site.

RaynorC1emen7
Expert

There is js that you have to put on your web page in order for it to access the code at authorize.net  This is the code that I need in an external file.

 

<!-- (c) 2005, 2012. Authorize.Net is a registered trademark of CyberSource Corporation --> <div class="AuthorizeNetSeal"> <script type="text/javascript" language="javascript">var ANS_customer_id="xxxdeletedIDxxx";</script> <script type="text/javascript" language="javascript" src="//verify.authorize.net/anetseal/seal.js" ></script> <a href="http://www.authorize.net/" id="AuthorizeNetText" target="_blank">Online Payments</a> </div>

 

My issue is that the src"//verify.authorize.net  is not valid and my web editor changes it.  It is well documented in the support forum that it has to be changed on the page at the server. My problem - the server does not allow direct editing and besides it would be stupid to go change the code in 100's of pages, just for it to be changed again the next time I uploaded changed files

you mean something like

http://any-expression.com/expression-web/tutorials/insert-include-pages.htm

 

I think you also could change the src="//verify.authorize.net/anetseal/seal.js" to src="https://verify.authorize.net/anetseal/seal.js"

NO, you cannot use "include" pages. If you have ever worked with FrontPage, that "include page" is input into your other pages as it is published.  So it would just change the authorize.net script on the page anyway.  And NO, you cannot change the "src" link. That is stated very specifically in the authorize.net support forum (which I already tried anyway with no success).

 

All I need is a javascript call from my page to load the external js file into my pages, unaltered.  I have tried every which way to call this file, but the file will not run. This leads me to believe that either authorize.net has something blocking this or the server my client is on does not allow the server to call external/off server js which is what the authorize.net javascript does.

 

So has anybody successfully done what I am trying to do, because of the way FrontPage/Expression Web changes the html source code? If you have, then I would appreciate knowing what your solution is.

tcertain,

 

It appears your web editor is modifying the html code copied from the merchant interface.  If you change 

 

src="//verify.authorize.net/anetseal/seal.js" 

 to

src="https://verify.authorize.net/anetseal/seal.js" 

 in your editor, it should correct the problem.

 

For more details, please see this support answer.

 

Richard

Thank you. It seems that the https  instead of http  was the reason I could not make it work - and for giving the link to the support section that I did not find, which was about Sitemanager, not FrontPage which says you can change the code

 

Sorry to Raynor - but the link to that specific article that I had found specifically stated that I was not allowed to change the code. It sure would have helped if I would have been pointed to that other support link.

 

But thanks to both of you, you have made my client happy!