Home Search Tags Members

Home » Kartris ASP.NET Ecommerce Software » Kartris suggestions » Check details before being passed to gateway.

Check details before being passed to gateway.

Posted By Neil Thu 4 Aug 2011
Add to Favorites0

Check details before being passed to gateway.

Topic View Topic View Topic Options Topic Options
Author Message
Neil
Posted Thu 4 Aug 2011
Supreme Being

Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)

Group: Forum Members
Last Active: Sat 3 Nov 2018
Posts: 192, Visits: 5,220
We have had a few issues with details being passed to our Gateway (SagePay) causing transactions to fail.

An example is here (delivery surname field too long) ...



==================================================

Callback Failure: VendorTxCode: XXXXXX<br/>Status: INVALID<br/>Status Detail: 3119 : The DeliverySurname value is too long.<br/>Amount: 56.18 GBP<br/>VPSTxId: {XXXXXXXXXXXXXXXXXXXXXXXXX}<br/>TxAuthNo: <br/>Address: , Post Code: , CV2: <br/>Gift Aid: No<br/>3DSecureStatus: &CardType=&Last4Digits=<br/>CAVV: <br/>

==================================================


Could these fields be checked before being passed to the gateway so the customer can correct them? I assume this would need to be done for each gateway?
Edited Thu 4 Aug 2011 by Neil
Post Information
Paul
Posted Fri 5 Aug 2011
große Käse

große Käse - (508,134 reputation)große Käse - (508,134 reputation)große Käse - (508,134 reputation)große Käse - (508,134 reputation)große Käse - (508,134 reputation)große Käse - (508,134 reputation)große Käse - (508,134 reputation)große Käse - (508,134 reputation)große Käse - (508,134 reputation)

Group: Administrators
Last Active: Tue 10 Sep 2024
Posts: 807, Visits: 2,748
It would be tough to extend per-gateway level validation to the checkout form; we'd have to have some framework to apply rules from the gateway to the checkout form, so we could validate lengths of field and so on there.

Maybe a simpler and better way would be to truncate the values to acceptable lengths before they're sent to the payment gateway. If Kartris is happy to accept a longer value, then it will go in fine, but will get trimmed on submission to Sagepay. In this case, the customer can then edit the value at sagepay.

Just out of interest, how long is the last name? I'd imagine sagepay has fairly long values, though clearly not quite as long as we allow.

--
If my post solves your issue, can you 'Mark as Answer' so it's easier for other users to find in future.

If you would like to be informed of new features, new releases, developments and occasional special bonuses, please sign up to our mailing list: http://bit.ly/19sKMZb
Post Information
Neil
Posted Fri 5 Aug 2011
Supreme Being

Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)Supreme Being - (123,363 reputation)

Group: Forum Members
Last Active: Sat 3 Nov 2018
Posts: 192, Visits: 5,220
It appears to be 22 characters long. Doesn't seem that long does it really?!
Post Information

Similar Topics

Expand / Collapse

Reading This Topic

Expand / Collapse

Back To Top

Powered By InstantForum.NET 2012-1 © 2024
Execution: 0.062. 8 queries. Compression Enabled.