Psyment authorization token testing broke our dev site

[lesliekirk]

Fixed

I'm going to tag into this because I am having an issue with Auth.net and the orders not making back to Miva. It probably have ZERO to do with the issue you had but that commented-out PaymentAuthorizationToken just slapped me in the face. Sorry if I'm hijacking your issue but maybe, just maybe it might have something to do with I'm trying to resolve.

[wajake41]

Fixed

[thilsabeck]

Hello Larry,

I apologize for the issue, we have received your ticket and will follow up with you though it.

Kind Regards,

[wajake41]

Still broken. Support is not taking any action on this.

[wajake41]

The issue:
Hello support: I tested the fraud authorization token on my dev.orange-traffic-cones.com site. Because of something I did? I can no longer view my basket page, When I attempt to view the basket page I am redirected to the OCST page. The dev site is now not usable because of this. Can you repair this someway?

Thanks, Larry


Replied to my ticket with Miva support. Here is what I think the issue is:
Hello support; Issue also exists on the boss's computer with has a different ip address, so this does not involve my ip address apparently.

I think something is amiss with the payment authorization fraud setting. This is the payment auth token on the OPAY page:

<!-- <div id="payment"><input type="hidden" name="PaymentAuthorizationToken" value="bf528de9a183f368a0b486f39bf42643"></div> -->

You can see that it is HTML commented. Consequently since it is not in the DOM, the authorization token will not be submitted to the server when page OPAY is submitted. Without the authorization token the payment processing cannot be done.

Please disabled whatever payment lock has been set on site dev.orange-traffic-cones.com apparently by the payment authorization setting.

Thank you, Larry