Anything that blocks their payment provider's script(s) from running will cause these errors. The issue is that SE's website redirects you to their processor's website just long enough to run the script(s), and then you are bounced right back to SE's website. It is very difficult to determine the payment processor's URL in order to simply allow their script(s) to run. Turning off all browser security temporarily should resolve many of the authorization errors that occur.