Hi @aleddy123,
I don't have the specific answers you are looking for, but I did notice that this appears to be the same issue reported in another forum post:
https://community.developer.authorize.net/t5/Integration-and-Testing/Iframe-communicator-loading-iss...
That said, I am currently working on a new intergration using the Accept Hosted payment form. From the start, I have decided not to fully trust in responses from the iFrame Communicator, since doing so relies entirely on javascript.
Our plan is to look for and process the iFrame Communicator response as a first approach, but to also create a fallback that relies on a Webhook. That way, theoretically, even if the iFrame Communicator response is never received, we should still receive notification of the transaction via the Webhook. The first response we get back (communicator or webhook) will be processed. We will keep track of the processing status to avoid processing the same transaction twice.
Obviously, if the communicator response is never received, that makes it difficult to present the user with an appropriate success confirmation, but at least the transaction will be properly processed in our system. Plus, we may institute a repeating ajax call in the payment parent page to check whether a matching transaction has been processed, which can in turn trigger delivery of a confirmation to the user if it finds that the transaction response has been received via Webhook. We did something similar for years with the SIM form and Silent Posts.
I hope this is helpful.