I just did a test order, Stripe works fine in Firefox, and in my previous tests all the other modern browsers were good with it too.
(our Stripe checkout uses jQuery).
I think the reason we included a google-hosted link to jquery.js is because we thought that would save us from having to update a locally stored jquery.js often since the remote one was likely to be more up to date, but I just checked and the one we're using hasn't been touched since 2013, so there's no real reason to do a remote include like this.
So I've replaced the HTML on the main page to NOT include jquery.js from that ajax.googleapis.com URL.
Instead, it will include a jquery.js that I just downloaded to the web server, so no more needing to whitelist any google hosts to order with bitcoin.
Just do a ctrl+F5 to refresh the page without loading from cache and everything should be fine.
, or you refreshed the token delivery page.
>>"Since there is no 'QR' payment system either, only an address, there is no trusted authentication (unlike the old Bitpay service)."
There is a QR feature in the Stripe checkout window though, just click that "Scan" button in the bottom right hand corning of the small window. That has nothing to do with trusted authentication though, nor did it whenever we were using Bitpay.
), and the "i" shows [email protected]
, and the life saver icon shows [email protected]
. Next to each email address (excluding [email protected]
) is a lock icon that links to our individual PGP keys if someone needs to send us an encrypted email. The reason I'm doing this semi-dynamic js/image style of displaying the email addresses is to help prevent automated email scrapers from easily obtaining our individual email addresses and spamming us.