Upon investigation, this appears to be a local browser cache issue, and we have not received any further errors since Friday, September 2nd. We will continue to monitor the results, but in the meantime, those who have encountered this behavior have resolved it on their end by completely clearing their browser cache, cookies, and local storage.
Posted Sep 06, 2022 - 08:37 CDT
We have received reports of some merchant's customers in Europe encountering CORS errors in their browser preventing Chargify.js fields from loading properly which may correspond with a non-functional internal release to Chargify.js earlier today. While this behavior does not appear to be widespread, out of an abundance of caution we wanted to provide a notice of these reports as our developers further investigate this behavior and the underlying cause.
So far, those who have encountered this behavior have resolved it on their end by completely clearing their browser cache, cookies, and local storage. This is the recommended resolution path at this time. We apologize for any inconvenience this causes and will provide another update as we have more information to share.