Showing results for 
Search instead for 
Did you mean: 

Accept.js - Exceptions regarding failure to load from CDN and bad CORS headers


I'm getting two errors when loading the library:


1)  XMLHttpRequest cannot load No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://[mydomain]' is therefore not allowed access.


2) Library is not coming from Accept CDN.


based on some posts from a previous thread here back in August (


I've tried not only loading the script as listed in the official documentation:


<script type="text/javascript" src="" charset="utf-8"></script>


This generates error #1 above related to the CORS origin headers.


I've also tried loading the script dynamically as recommended by the moderator on the thread by doing this:


$(document).ready(function () {
        $.getScript(jsUrl, function (data, textStatus, jqxhr) {
dispatchEvent(new Event('load')); GetScriptCallback(); }); });


and this generates both of the errors listed above.


Since both errors appear to be blocking issues, I can't seem to get past it, so at the moment I'm dead in the water.


From the thread I cited above, it seems these errors just magically stopped happening for some folks and then came back randomly and then stopped again and so on.  It seems I'm at a point where they are reappearing.


I'm not sure what the status of the Accept.js library but based on the open threads and the errors I'm stills seeing 2 months later it seems like somebody shipped it before it was ready for primetime.


Nonetheless, I've now got a client who is looking to get up and running with it next week and I'm stuck sorting out these errors so I'd appreciate some assistance.


Any updates on what the latest code or documentation is for this library?


Accepted Solutions

Kris and Jeff, make sure your passing in a string for the second parameter for dispatchData and not the actual responseHandler method.


I'm coming from the Stripe world where you just pass in the responseHandler method and your done, but this requires you to pass in the name of the method as a string and then define the responseHandler as a global function that can then be found by window[c].


Kind of unorthodox and a pain to deal with, but once i adjusted for that I got it to work.


Invoking Call:

Accept.dispatchData(secureData, 'handleAuthnetResponse');

Note the second parameter is a string, not a variable.





  window.handleAuthnetResponse = function(response) {
    var error_messages = '';
    var error_container = '';

    if (response.messages.resultCode === 'Error') {
      for (var i = 0; i < response.messages.message.length; i++) {
        error_messages = error_messages + response.messages.message[i].code + ':';
        error_messages = error_messages + response.messages.message[i].text + '<br/>';

      error_container = '<div class="alert alert-danger"><a class="close" data-dismiss="alert">×</a>' + error_messages + '</div>';

      $authnetRoot.find('button[type=submit]').prop('disabled', false);
      $authnetRoot = null;
      return false;
    else {

      return true;


View solution in original post


I'm getting this same CORS error, followed by:

AcceptCore.js:1 Uncaught TypeError: window[c] is not a function(…)


...when I try to submit. :-(


krisajenkins - I'm also seeing that error regarding window[c] as well.  It seems to happen only when i actually call the dispatchData method.


Any updates from the admins on any of this? 

Hello @describeit


Sorry for the delay, it was a holiday for us last Friday.  I've notified our product team about your issue.



Thanks Richard, I'll keep an eye out for a response.

I am having this same issue.  I decided to install the accept-sample-app from the github project, and it has the same issue:


XMLHttpRequest cannot load No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '' is therefore not allowed access.


My project is completely dead in the water due to this bug. 


Thank you,


Admins any updates on this?


Is anyone successfully using this library?


FYI - I received an email from support yesterday asking me to ensure I was declaring UTF-8 charset on the page and the script include.  I am doing both already and its still producing the error.


<meta http-equiv=“Content-Type” content="text/html; charset=utf-8">

<script type="text/javascript" src="" charset="utf-8"></script>


Still produces:


XMLHttpRequest cannot load No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin ‘' is therefore not allowed access.

Hi guys,


I have a very simple test page hosted at, the source is on github at 


Note that if you open a js console you will see the CORS error on load, that one is due to the internal core library not being available for external access, it does not impact processing but it is unfortunate that the error presents.  I have shown this error plus the successful nonce returned in the screen shot below.


Hope this helps but please let me know if not and we can continue troubleshooting,





Hi Brian,


  Thanks for the response.  I've used your code and gone line by line through it.  I'm getting much farther but its still failing.


  The error occurs on line 181 in the AcceptCore.js file.  In the compressed/minified code it reads as




If I put a breakpoint on that line, window[b] is in fact undefined.  b itself looks to contain the responseHandler method and c accurately contains a successful response with a payment Nonce included.


Since b is an input parameter to the method, why is it being accessed via window[b] instead of just b?  If I call b(c) that works, but unfortunately its happening inside of AcceptCore.js which I can't change.


PS - I'm loading the script tags in the HTML head tag just like in your example, but my execution is a bit more complex than your example.  I'm invoking the script from within a RequireJS module in a function that is invoked by an .on('submit') event listener.


Is it possible that this is causing part of the problem?  I don't even know where to begin debugging that, but woudl love to know why your referencing the callback handler from within the window array.

Thanks for the response brianmc, but I'm afraid it doesn't help. I get that CORS error, ignore it, and when I call dispatchData I get that window[c] error posted above.


My setup is much simpler than describeit's, but it looks like it's broken either way. :-(