Protx VSP Direct v2.0.0

I have installed version 2.02 for Zen 1.2

I have got two questions:

First under admin it says You do NOT have PEAR:Crypt/Blowfish installed on your server!

I am pretty sure it is, when I do linux command "pear list" I get Crypt_Blowfist v. 1.0.1 stable installed.

I tried to to transaction in debug mode and it says Encryption NOT USED!

Any ideas how I can work out this problem.

Second question. When I am at the checkout payment page I get this in front of the cards images:

MODULE_PAYMENT_PROTX_DIRECT_TEXT_CREDIT_CARDS_ACCE PTED

And in the drop down menu for selecting credit cards:

MODULE_PAYMENT_PROTX_DIRECT_TEXT_VISA

Regards,

Baldur

Hi Baldur,

Quote:

---

Originally Posted by ofurbaldur

I tried to to transaction in debug mode and it says Encryption NOT USED!

---

If you are getting that message then PEAR:Crypt_Blowfish cannot be accessed by your php installation. This could be because it isn't actually installed, PEAR isn't on your include_path or you have an open_basedir restriction in effect which doesn't allow your php installation to use PEAR files - all three of these situations are a lot more common than I would have thought!

Please send me the debug output from a test transaction so I can see why you aren't able to use the encryption (e-mail address is on the website).

Quote:

---

Originally Posted by ofurbaldur

Second question. When I am at the checkout payment page I get this in front of the cards images:

---

Have you modified the languages file in any way?

(/includes/languages/english/modules/payment/protx_direct.php)

Somehow the full file isn't being loaded... it sounds like you have a corrupted file (extraneous apostrophe or quote somewhere maybe)?

Try copying all the files across again, overwriting the existing ones!

Hope that helps...

Quote:

---

Originally Posted by pixxi

By the way, do the two 'contact us' links defined in the protx_direct language file (near the bottom) work for you?

---

Oops, don't know how I missed that one. Fixed in 2.0.3.

Quote:

---

Originally Posted by pixxi

It might also be better not to have the merchant's Protx vendor name appear on the first of those error messages - maybe just the general message (eg. 'vendor name not recognised') instead?

---

Unfortunately that's not an option... that is the error message sent back from Protx. This should never happen on a live site though as any testing of the module before the site goes live would show this particular problem up quite easily!

Will be releasing 2.0.3 shortly, so if there's anything else you have found (thanks! :) )....

All the best...

Conor

Hi Conor,

Quote:

---

Unfortunately that's not an option... that is the error message sent back from Protx. This should never happen on a live site though as any testing of the module before the site goes live would show this particular problem up quite easily!

---

Ok. And (presumably) if you removed the 'extraerrorinfo' section from the end of that first define (which removes the 'vendor name' error info sent from Protx) you would also lose other specific error information returned from Protx that the customer might need to see?

Fine, it can stay then :yes:

Another small thing ...

1. Do you find the Visa test card number goes through the test server Ok? I'm consistently getting a 'card number error' from Protx. Real Visa card numbers go through fine.

(BTW, if anyone else gets the 'vendor name not recognised' error, it can be caused by having Amex turned on in the Protx mod in the shop admin, and processing an Amex card number when you don't have Amex enabled on your Protx account, or, of course, by having the wrong vendor name entered in the Protx mod :smile: - but as Conor says, it should never happen live unless you accidentally change your settings for vendor name or Amex on the mod in the shop admin)

Hi,

A slightly updated version of the module has been released due to user feedback!

Here's the snippet from the Version History:

Quote:

---

[UPDATED] The Language Definitions file has been extensively updated to use “Credit/Debit Card” where appropriate, rather than using “Credit Card” exclusively all the time.

[UPDATED] “UK Maestro” is now identified simply as “Maestro”.

[UPDATED] The Card Type on the Confirmation page now uses full text rather than Protx's Card Type codes.

[UPDATED] FAQs have been added the documentation due to the increasing volume of e-mail about particular issues.

[BUGFIX] The Debug Mode was ignored if an error occurred during the cURL transaction, now it runs and outputs correctly.

[BUGFIX] The Contact Us links in error messages didn't link to the correct address.

---

It is recommended that everyone using this module upgrade immediately as although the changes are minor, they may help make things clearer for your customers! Plus the "Contact Us" link working is quite handy if a customer experiences problems with Protx (although that's rare once you've configured the module properly).

Full Upgrade Instructions are available on the website and in the updated documentation!

You can always find the latest versions at the contribution's site:

http://dev.ceon.net/web/zen-cart/protx_direct

Enjoy!

All the best...

Conor
ceon

Hi Conor,

Thanks for the rapid update :)

Two more small points that have emerged:

1. When you put a test transaction through on the Protx test server using the JCB test card number (assuming you have JCB enabled on your Protx account, and this account does have) the transaction is successful but the Protx results page says that the house number, the postcode, and the CVV 'were not provided'. All test transactions using any of the other test cards show green ticks (AVS and CVV successful).

2. It would be useful to also have the JCB and Electron test card numbers displayed on the mod in the shop admin (along with the test card numbers that are already displayed there) for people who want/need to test those numbers. Protx don't seem to provide the complete list of card test numbers until after you've confirmed completion of live testing (very useful :) ).

Thanks again for you help :)

Hi,

Quote:

---

Originally Posted by Pixxi

Thanks for the rapid update :)

---

Always aim to please! ;)

As far as the JCB AVS checking goes, I'm guessing it may simply not use it? I really don't know because I have no idea what a JCB card is! :)

We don't have a live account ourselves, just a test one Protx set up because I maintain this module. I could ask my clients for the numbers you mentioned but they'd probably have to look all over the place to find them... do you mind just e-mailing them to me and I'll add them in for the next version? Thanks :)

All the best...

Conor
ceon

Hi Conor,

1. The JCB AVS/CVV not showing was apparently a problem at Protx's end. Just received this reply from support:

Quote:

---

1. This was an issue with the Protx Test server. JCB is a new concept on our system, so we have just corrected that now for you. (thanks for letting us know.) Please test again and let us know if you have any further issues.
NB: We pass the AVS & CV2 results for JCB cards, it is then up to the card issuer to provide the results.

---

2. The test Visa number has been confirmed as correct and working by Protx - so not sure why it gave me 'card error' each time on the test server - but as I said, real Visa numbers went through fine, so no problem. Just a note in case anyone else has it happen.

3. I'll PM you the test numbers for JCB and Electron - would have sent them before but thought you had them already.

Thanks again for your help :)

Hi,

Quote:

---

Originally Posted by Pixxi

1. The JCB AVS/CVV not showing was apparently a problem at Protx's end. Just received this reply from support:

---

Good to know that that's sorted, thanks!

Quote:

---

Originally Posted by Pixxi

2. The test Visa number has been confirmed as correct and working by Protx - so not sure why it gave me 'card error' each time on the test server

---

That's weird... just put my own test through on the test server and, as always, it's working fine for me. Hmmm... if real Visa cards work though then that's the main thing! :P

Quote:

---

Originally Posted by Pixxi

3. I'll PM you the test numbers for JCB and Electron - would have sent them before but thought you had them already.

---

Got them, thanks.

I'll add them into the current distribution of 2.0.3, don't think it's worth advancing the version or announcing an update for something as small as that!

All the best...

Conor
ceon

Hi Conor,

Test Visa number resolved too - user error coupled with a non-standard approach on that particular test number by Protx.

Visa numbers are (as you know) 16 digits, but Protx uses 13 digits for that test number for some reason. We didn't count the zeroes, just assumed there were 11 when in fact there were 8 - hence the error we had. :smile:

Thanks again :smile:

Hi Conor,

Just had an odd thing happen with a customer using the Protx mod (v.1.2.x).

The customer would seem to have clicked the final 'confirm' button on checkout twice and generated two identical orders in the shop (the orders were timed 4 seconds apart and had consecutive order ID's).

Obviously the transaction ID info was unique, just the items ordered were the same. Both orders went through Protx so the customer was charged twice.

The shop has had a notice next to the 'confirm' button advising the customer to 'only click once then wait' since the mod was installed, but obviously some customers don't read notices :smile:

Would it be possible to disable the action of the 'confirm' button (for that particular customer, maybe based on session ID) once the customer has clicked it to prevent this happening?