Reply
Highlighted
Member
Posts: 6
Registered: ‎06-14-2019

Potential Hosted Payment Page Bug

I have been running into some issues in getting a hosted payment page to work in sandbox mode, and am hard-pressed to find any explantion besides that it might be a bug. I've been able to request a auth token and redirect to the hoseted payment page just fine, the issue came into play when I started adding GET parameters to the return url. (Where the hosted payment page would redirect users back to my site.) Before it was a proper hosted payment page that would allow me to fill in the info & redirect back to my site. Afterwards, the token request still works, the only thing on the hosted payment page is a header saying 'Order Summary' I changed nothing besides the url in the hostedPaymentReturnOptions, in the call to get a token. My parameters are url encoded, so I see no reason why the additional parameters would be an issue.

 

Working return url:

http://mysite.com/gpayment/process?g=8

 

Malfunctioning return url:

http://mysite.com/gpayment/process?g=8&i=4R5Kkj1meVuqOEIe92N9O6igSY5KtQ%3D%3D&a=cbc8ecc1bf36f64237ea...

Highlighted
All Star
Posts: 727
Registered: ‎11-05-2018

Re: Potential Hosted Payment Page Bug

@gratdevtech

Auth.net tends not to like parameterized return urls for anything. If I recall correctly, parameterized urls will work for the Accept Hosted return url and/or cancel url, however. Seems like I tried this and I vaguely remember that the cancel url wouldn’t accept one but the return would.

For your url, do you think it is possible you are exceeding character lengths with the long query string?
Highlighted
Member
Posts: 6
Registered: ‎06-14-2019

Re: Potential Hosted Payment Page Bug

As far as I can tell, it wasn't a character limit issue. I could have a single parameter of some length, but if my return url had two parameters, the page simply contained a header. Rather disappointing.