Actually in our case the problem was a little different. We were using
the same domain in the iframe communicator URL as the app uses, but the
iframe communicator URL has a query string on it that included the caret
(^) character. That had been used ...
We have had reports of this issue, but haven't been able to track it
down yet. Can you be a little more specific about how you are receivng
the response from Authorize.net? We are using the
hostedPaymentIFrameCommunicatorUrl setting in the
getHostedP...
I have a question about the transaction key vs the signature key. This
page:
https://support.authorize.net/s/article/Do-I-need-to-upgrade-my-transaction-fingerprint-from-HMAC-MD5-to-HMAC-SHA512-and-how
says that the signature key is used to create th...
I seem to have hit the same problem. In my case, the payment form is
embedded in an iframe and I am sending an iFrameCommunicator URL in the
token request. The payment form would work in Firefox (54.0.1), but not
in Chrome (60.0.3112.90). In the Chro...
I'm having a similar problem trying to post to the following URL from a
machine running Windows Server 2008:
https://apitest.authorize.net/xml/v1/request.api The socket can be
opened, but trying to start encryption results in the server resetting
the...
