TOPIC: [SOLVED] Authorize.net payment popup is cut off at top of page

Once someone is passed to Authorize.net to pay now, it is opening a popup (used to go to an Authorize.net page) and the top half of the popup is cutoff so people cannot see and enter the information needed to pay.

Yes, the new API integration uses a popup. It is still the Authorize.net page, but loading there in the popup instead of a full page redirect. Same thing though, and an official integration of the new Accept Hosted API.

If it's being cutoff somehow, you must have something within your template CSS that is affecting it. We haven't seen that scenario yet. I'm sure it can be addressed via CSS though. If you can't track down what is causing it, put it in a ticket and we'll take a look.

nathan.dth wrote: Yes, the new API integration uses a popup. It is still the Authorize.net page, but loading there in the popup instead of a full page redirect. Same thing though, and an official integration of the new Accept Hosted API.

If it's being cutoff somehow, you must have something within your template CSS that is affecting it. We haven't seen that scenario yet. I'm sure it can be addressed via CSS though. If you can't track down what is causing it, put it in a ticket and we'll take a look.

Thanks for looking into this. I updated my ticket; the window is cut off some at the top in Firefox and Edge. Hopefully, we can come up with a solution for different browsers as not all use Chrome. Thanks.

This was addressed in your ticket. For anyone else that might see this issue (unlikely), it was not a DT Register problem... nor a browser issue. It was a template issue. It has a z-index for the header elements that was extremely high so it would lay on top of anything else. IF a screen size was small enough where the height of all of it together wouldn't fit, then the Authorize.net popup would get shoved under the big z-index header. Adjustments could be made to the z-index of the header elements OR to the popup. I gave further details in the ticket.

Thanks, Nathan. I will take a look at the template coding!