I use a gateway which if you post additional fields which it is not expecting will fail the transaction with "invalid card number" (I think it believes that additional form fields mean it's the customer entering card details).
Ideally we should have the gateway provide some way of telling Nexus on the front end to not include those fields. Currently I'm getting around it by returning </form> and a new form entirely in the buttonHtml response.
I'd also really like to see some way of changing methods without AJAX since there's currently a couple of seconds wait where a customer could click on "Confirm My Order" and bomb their transaction.
When overriding formUrl in custom gateways, don't include hidden fields in form
Started by Kyanar, Aug 08 2012 06:25 AM
No replies to this topic
#1
Posted 08 August 2012 - 06:25 AM
Mat / Fusion Digital Entertainment Limited
Our Website: http://www.fusiondigital.co.nz/
Our Forums: http://community.fusiondigital.co.nz/
Our Website: http://www.fusiondigital.co.nz/
Our Forums: http://community.fusiondigital.co.nz/
Chronicle, the desktop time tracker for Windows • Fusion Menu, the leading navigation enhancement application for IP.Board • CommunityContact, the in development community newsletter application
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users











