cancel
Showing results for 
Search instead for 
Did you mean: 

Authorize.Net Accept Hosted Lightbox Triggering Automatically on WooCommerce Checkout Page Load

Screenshot 2025-10-09 at 8.41.47 PM.jpgI’m using the official WooCommerce Authorize.Net Payment Gateway extension with the Accept Hosted integration method. On the checkout page, the payment lightbox automatically appears as soon as the page loads, blocking customers from filling in their billing and shipping details.

Expected behavior:
The payment lightbox should only appear after the customer has entered their information and clicked “Place Order.”


Troubleshooting Steps Taken

I’ve already completed standard troubleshooting steps to isolate the issue:

  • Plugin Conflict Test: Deactivated all plugins except WooCommerce and Authorize.Net Gateway the issue persisted.

  • Theme Conflict Test: Switched to the default Storefront theme the issue still occurred.

  • Cache Clearing: Cleared all site, server, and browser caches multiple times.

  • API Credentials: Verified that the API Login ID, Transaction Key, and Signature Key are correct.

  • Authorize.Net Settings: Checked my Authorize.Net merchant account to ensure no required fields on the hosted payment form are enforcing premature submission.

  • Debug Logs: Enabled logging in the WooCommerce Authorize.Net plugin. Logs show normal activity with no specific errors or conflicts indicating early lightbox triggering.


Observations

The issue appears to stem from a JavaScript event or endpoint being triggered prematurely. Since plugin and theme conflicts have been ruled out, it seems to be a deeper integration issue possibly related to how the Accept Hosted JavaScript is being initialized or loaded on the checkout page.


Questions for the Developer Community

  1. Are there any known JavaScript hooks or iframe events within the Accept Hosted integration that could be unintentionally triggered by other scripts?

  2. Could this behavior be linked to a particular version of WordPress, WooCommerce, or a server configuration affecting the timing of script execution?

  3. Has anyone else experienced this issue and found a solution beyond standard conflict resolution steps?

Itse
Member
0 REPLIES 0