Title: Authorize.net Issue Last modified: January 14, 2021 --- # Authorize.net Issue * Resolved [richsadams](https://wordpress.org/support/users/richsadams/) * (@richsadams) * [5 years, 5 months ago](https://wordpress.org/support/topic/authorize-net-issue/) * One of my sites is suddenly experiencing a problem with accepting credit card payments using the SG Optimizer and WooCommerce Authorize.Net Gateway plugins. The debug report shows the following error: * “Accept.js Error: payment nonce is missing” * I tested all of the settings and in order to accept credit card payments I’ve had to deactivate all SG Optimizer JavaScript Frontend optimizations (Minify, Combine and Defer). The error is present if any one of them are activated. * I noted that this was an issue eight months ago and was said to be resolved here: [https://wordpress.org/support/topic/sg-optimiser-and-authorise-net-woocommerce-plugin/](https://wordpress.org/support/topic/sg-optimiser-and-authorise-net-woocommerce-plugin/) * I would like to use these optimizations but it looks like this is an issue again. Can you help with this? * TIA! * WP Version 5.6 WooCommerce Authorize.Net Gateway Version 3.4.0 SG Optimization: Version 5.7.12 Host: SiteGround * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fauthorize-net-issue%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 7 replies - 1 through 7 (of 7 total) * Plugin Author [Hristo Pandjarov](https://wordpress.org/support/users/hristo-sg/) * (@hristo-sg) * SiteGround Representative * [5 years, 5 months ago](https://wordpress.org/support/topic/authorize-net-issue/#post-13906059) * Did you try excluding it by using the plugin functionality? * Thread Starter [richsadams](https://wordpress.org/support/users/richsadams/) * (@richsadams) * [5 years, 5 months ago](https://wordpress.org/support/topic/authorize-net-issue/#post-13906077) * Thanks for the fast reply! * Yes, but as soon as I activate “Defer” the problem returns. * Welcome your thoughts and thanks again! * Plugin Author [Hristo Pandjarov](https://wordpress.org/support/users/hristo-sg/) * (@hristo-sg) * SiteGround Representative * [5 years, 5 months ago](https://wordpress.org/support/topic/authorize-net-issue/#post-13906094) * Well, don’t defer that script, it might not work deferred. * Thread Starter [richsadams](https://wordpress.org/support/users/richsadams/) * (@richsadams) * [5 years, 5 months ago](https://wordpress.org/support/topic/authorize-net-issue/#post-13906114) * Thanks, I’ve tried both ways, deferred, not deferred, etc. As soon as “Deferred” is activated with or without any scripts, the site will not accept credit cards and the log shows the “Accept.js Error: payment nonce is missing” error. * The same goes for any/all of the JavaScript optimization settings. Whenever any are activated the error instantly appears. * The cart page displays this error to the customer: * “An error occurred, please try again or try an alternate form of payment.” * Thanks again. - This reply was modified 5 years, 5 months ago by [richsadams](https://wordpress.org/support/users/richsadams/). - This reply was modified 5 years, 5 months ago by [richsadams](https://wordpress.org/support/users/richsadams/). * Plugin Author [Hristo Pandjarov](https://wordpress.org/support/users/hristo-sg/) * (@hristo-sg) * SiteGround Representative * [5 years, 5 months ago](https://wordpress.org/support/topic/authorize-net-issue/#post-13906215) * As said, if it is working non-deferred keep it that way. If you want it to work deferred, please contact the Autorize net plugin developers. * Thread Starter [richsadams](https://wordpress.org/support/users/richsadams/) * (@richsadams) * [5 years, 5 months ago](https://wordpress.org/support/topic/authorize-net-issue/#post-13906253) * Thanks. * FWIW, the issue arose yesterday. No changes were made to the site. No changes were made to SG Optimizer settings. The site just suddenly stopped accepting credit cards. Deactivating SG Optimizer immediately fixed the problem. After experimenting with the SG Optimizer settings it turned out that the JavaScript optimization functions were the issue. Deactivating all three resolved the problem. Activating any one of them causes the problem to return. * AFAIK, Authorize.net did not change anything on their end either. * As posted above, the exact same issue was occurring for another user 8 months ago and was said to be resolved. * So I’m not sure what to do next. The impact on the site causes it to load slower, but it’s livable. Hopefully the next version of SGO will resolve this. * BTW, posting that the issue is resolved is incorrect. * Thanks again. - This reply was modified 5 years, 5 months ago by [richsadams](https://wordpress.org/support/users/richsadams/). * Plugin Author [Hristo Pandjarov](https://wordpress.org/support/users/hristo-sg/) * (@hristo-sg) * SiteGround Representative * [5 years, 4 months ago](https://wordpress.org/support/topic/authorize-net-issue/#post-13907407) * I am sorry but as I said it is not even a SG Optimizer issue. Please, open a thread in their plugin in order to get further assistance or keep this optimization disabled for that script. Viewing 7 replies - 1 through 7 (of 7 total) The topic ‘Authorize.net Issue’ is closed to new replies. * ![](https://ps.w.org/sg-cachepress/assets/icon-256x256.gif?rev=2971889) * [Speed Optimizer - The All-In-One Performance-Boosting Plugin](https://wordpress.org/plugins/sg-cachepress/) * [Support Threads](https://wordpress.org/support/plugin/sg-cachepress/) * [Active Topics](https://wordpress.org/support/plugin/sg-cachepress/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/sg-cachepress/unresolved/) * [Reviews](https://wordpress.org/support/plugin/sg-cachepress/reviews/) ## Tags * [authorize.net](https://wordpress.org/support/topic-tag/authorize-net/) * 7 replies * 2 participants * Last reply from: [Hristo Pandjarov](https://wordpress.org/support/users/hristo-sg/) * Last activity: [5 years, 4 months ago](https://wordpress.org/support/topic/authorize-net-issue/#post-13907407) * Status: resolved