topic Re: Issues with iFrameCommunicator in Integration and Testing

Issues with iFrameCommunicator

tfreeman — Wed, 20 Mar 2019 01:04:24 GMT

I am having an issue with the hosted payment form sending some events to the iframecommunicator.

Resize events get sent correctly:

E.G.
https://local.bizlock.net/payment/authnet/iframe-communicator/payment#action=resizeWindow&width=442&height=1061.22

But the url for transactResponse is being truncated after the first '{'

E.G.

https://local.bizlock.net/payment/authnet/iframe-communicator/payment#action=transactResponse&response={

This is an only an issue for the first event since only the first event is sent by loading a url with the event data in the url fragment identifier.

You also do not check to make sure the iFrameCommunicator iframe is loaded before you try to send messages to it. This leads to a "Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://local.bizlock.net’) does not match the recipient window’s origin (‘https://test.authorize.net’)." error. You also don't catch and retry sending messages so they will be lost when they are sent before the iFrameCommunicator has loaded.

Re: Issues with iFrameCommunicator

tfreeman — Mon, 25 Mar 2019 00:45:27 GMT

Part of the issue is the the hosted payment form (as opposed to the hosted profile forms) does not load the iFrameCommuncator prior to dispatching its first event. This means that if the first and second events fire in rapid enough succession vs. any network delay, the second event is lost.

This also means that the first event fired by the hosted payment form is often the 'transactResponse' event which is sent via the document fragment identifier in the url rather than via a JS postMessage event. This means that the necessary information needed from the 'transactResponse' payload is missing and we are unable to send the customer on to the next part of the checkout process.

Re: Issues with iFrameCommunicator

daves0 — Tue, 23 Jul 2019 22:25:30 GMT

Any response from Authorize.Net here? These are significant issues, and a resolution has been suggested...

Re: Issues with iFrameCommunicator

satheesh22 — Wed, 24 Jul 2019 11:53:52 GMT

Refer this :

https://community.developer.authorize.net/t5/Integration-and-Testing/AUthorize-net-hosted-payment-page-not-working-in-Chrome-Version/m-p/59271/highlight/true#M33867

Re: Issues with iFrameCommunicator

Wei — Wed, 30 Dec 2020 07:20:05 GMT

Guys,

after severals days headache, confusing and depressing, we figured it out!

this intermittent issue is due to how we(the integrator) use the hosted form, that is render hosted form too earlier cause listener not registered.

inside the hosted form

<div _ngcontent-c0="" class="iFrameClass" id="divIframeCommunicator"></div> is not fully rendered.

<div _ngcontent-c0="" class="iFrameClass" id="divIframeCommunicator"><iframe src="your_site_url" name="ifrmCommunicator" id="ifrmCommunicator"></iframe></div> the correctly one.

the symptom is unable to receiveMessage but location.hash give truncated JSON like "#action=transactResponse&response={"

also noticed their demo page in doc is a button to trigger post form token, where is an implied delay.

when realized this the solution is simple, instead of do $("#send_token").submit(); in .ready() but do it in setTimeout with 1-2 seconds delay.

now the hosted iframe working perfectly under Firefox, Chrome, Edge, IE11 and Opera

From avetticommerce