Protx VSP Direct 3.x

[doubletiger]

Hi,

I have been used Protx Direct for a while, it works very well. Tahnk you ceon! However, recently, when the cusomer use Visa Debit card from Halifax and put the issue no in, the web page went blank. the URL will become "index.php?main_page=checkout_payment&payment_error=protx_direct&error=|lt%3B|h3 +class%3D%22ErrorInfo%22|gt%3B|Your+card+could+not+be+authorised!+Please+correct +any+details+below+and+try+again%2C+try+another+card+or+|lt%3"

this also happen to Maestro card as well. It seems the somehow, the module cannot handle this kind of error. But I believe the mudule has worked before, it gave error warning in red colour wording if such error occured. I suspect might be I changed codes somewhere it break the module, but I cannot figure it out. This was happened to Protx version 3.42 and I have upgraded to version 3.61, but the problem still here.

The module is still working only if the customers put all of card information correctly.

Have any Protx user got similar issues?

How can I figure it out?

thank you in advance!

[conor]

Hi Henry,

I don't think the module's failing but instead the code on your site which is supposed to be outputting error messages seems to be failing and causing a PHP error (which - with error reporting turned off - appears as a blank page!).

Please get in contact with me privately, sending me some temporary FTP and admin details and I can log in and take a quick look to see if I can see what's gone wrong!

All the best...

Conor
Ceon

[doubletiger]

Thanks to Conor, the problem has been fixed. It was some bad codes outside the module which preventing the module from working correctly. This is another example which proves this Protx Direct module is a well-coded module. Also, the owner of this module, Conor, he is not only a genie in coding, he is also a very kind person who always stepping to help if he can! I am glad I've chosen this module. Thank you very a million to Conor!

[crazycucumber]

Hi Conor , I have bought / installed and running your ( ver 3.6.0 ) Mod now for 2 weeks , I have just looked through our transaction logs on VSP and some of the address matching is failing . On the transaction report , it looks like the first line and last line of the address are the only ones to be send to Protx , I wonder if this is why the address does not match . Is this normal ? the transactions are still processing as they match on the post code.

Is this something I should ask Protx about ? Thanks for any advice.

Mark.

[CES]

Hi

Conor would probably elaborate more, but from:

http://en.wikipedia.org/wiki/Address...ication_System

'AVS verifies the numeric portions of a cardholders billing address. For example, if your address is 101 Main Street, Highland, CA 92346, AVS will check 101 and 92346.'

I hope this helps.

Craig

[conor]

Hi Mark,

I have just looked through our transaction logs on VSP and some of the address matching is failing . On the transaction report , it looks like the first line and last line of the address are the only ones to be send to Protx

As far as I know the algorithm used to perform the address matching is extremely limited to the point of being fairly useless.

It gets the digits from the first line of the address and the digits from the postcode, combines them and performs the check against that.

We ourselves noticed lots of fails with AVS matching enabled so we have had it disabled for the past year and a half and rely solely on CV2 code and 3D-Secure.

I wonder if this is why the address does not match

No, it isn't. It's the fact that many people enter free text addresses differently.. only the first line is used so if they enter something "strange" [unexpected] there (a house name or flat number instead of the street number for example) then the match will fail.

It's a bit annoying that the algorithms are so limited but we've found CV2 code checks (plus additional 3D-Secure checks when appropriate) to be more than reliable, with not one false transaction reported to us yet.

What level of checking you use is of course up to you, I'm just letting you know my own personal thoughts on this.

Hope that helps!

(Thanks Craig for your input while I was in the middle of replying! ;) )

All the best...

Conor

[conor]

Hi,

We set up our Account parameters in the VSP admin as follows:

Allow No Data Matches

Allow Address Match Only

Allow CV2 Match Only

Allow Data Not Checked

Allowing Address Match Only results in failed transactions.

Obviously we don't want to allow no data matches.

Data not checked sounds ominous but is unlikely to be used, it's a fallback for banks that don't check the data. I'm not aware of any that operate like this any longer (there used to be some years ago though).

All the best...

Conor

[crazycucumber]

Thanks all for the promt replies .. I will go through and check my settings . We have not turned on 3d secure as yet as we launched in a hurry and not had time to run a few tests yet. hence we are keeping a close eye on the transactions at the moment. Thanks again for the reassurance.

All the best
Mark .

[athenadesign]

Hi!

Having implemented the ProTX module (which by the way, just plugged in to zen cart with no issues) and done all the tests via the simulated protx server, however now we are on the live server we can process normal payments, however when we switch on 3D-Secure we get a 406 error, any ideas?

Thanks!

[Brent]

Which version are you using? You need 3.6.1 for 3D support.

Regards,

Brent