The Global Payments HPP embedded payment flow continuously reloads on Chrome on iPhone and the payment page never completes loading.
The issue only occurs on iPhone Chrome. The same integration works correctly on other tested browsers.
During iframe initialization, the callback passed to RealexHpp.embedded.init() is triggered before any payment interaction.
On iPhone Chrome, the callback passed to RealexHpp.embedded.init() is invoked during iframe initialization before any user interaction. The callback receives:
{
"error": true,
"message": {
"command": "registerAsChildFrameAck",
"remoteFrameId": "<dynamic>"
}
}
This appears to be an internal iframe initialization/communication message rather than an actual payment response.
The issue seems isolated to Chrome on iPhone, as the same flow works on iPhone Safari and iPhone Edge.
Is registerAsChildFrameAck expected to be returned through the callback during iframe initialization?
Could this message indicate an iframe registration/communication issue specific to Chrome on iOS?
The Global Payments HPP embedded payment flow continuously reloads on Chrome on iPhone and the payment page never completes loading.
The issue only occurs on iPhone Chrome. The same integration works correctly on other tested browsers.
During iframe initialization, the callback passed to
RealexHpp.embedded.init()is triggered before any payment interaction.On iPhone Chrome, the callback passed to
RealexHpp.embedded.init()is invoked during iframe initialization before any user interaction. The callback receives:This appears to be an internal iframe initialization/communication message rather than an actual payment response.
The issue seems isolated to Chrome on iPhone, as the same flow works on iPhone Safari and iPhone Edge.
Is registerAsChildFrameAck expected to be returned through the callback during iframe initialization?
Could this message indicate an iframe registration/communication issue specific to Chrome on iOS?